<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://alexandria.anarchaserver.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thf</id>
	<title>Anarchaserver - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://alexandria.anarchaserver.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thf"/>
	<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php/Special:Contributions/Thf"/>
	<updated>2026-05-17T19:48:39Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.36.1</generator>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=248</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=248"/>
		<updated>2016-07-16T16:31:38Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* TransHackFeminist Convergence */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
== TransHackFeminist Convergence  ==&lt;br /&gt;
&lt;br /&gt;
The TransHackFeminist convergence is a 7 day event that was organised for the first time in Calafou (Catalonia) in August 2014. A second edition will be held from the 25 to the 31 of May in Puebla 2015 (Mexico).And 2016Third TransHackFeminist is coming https://femhack.noblogs.org/thf-2016/&lt;br /&gt;
You can find [[documentation about the THF 2014]] and about how to engage and get involved in the preparation of the [[third edition in this section]]. &lt;br /&gt;
&lt;br /&gt;
[[File:424px-8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
[[File: THF2016.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:thf1.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
Anarchaserver is a feminist server which aim is to develop autonomous infrastructure on the Internet for feminists projects. You can find documentation about how to engage and get involved in the server in the [[Anarcha section]].&lt;br /&gt;
&lt;br /&gt;
[[File:Marina Ginesta.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== What do I need to know about wiki ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=247</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=247"/>
		<updated>2016-07-16T16:28:50Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* TransHackFeminist Convergence */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
== TransHackFeminist Convergence  ==&lt;br /&gt;
&lt;br /&gt;
The TransHackFeminist convergence is a 7 day event that was organised for the first time in Calafou (Catalonia) in August 2014. A second edition will be held from the 25 to the 31 of May in Puebla 2015 (Mexico).And 2016Third TransHackFeminist is coming https://femhack.noblogs.org/thf-2016/&lt;br /&gt;
You can find [[documentation about the THF 2014]] and about how to engage and get involved in the preparation of the [[second edition in this section]]. &lt;br /&gt;
&lt;br /&gt;
[[File:424px-8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
[[File: THF2016.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:thf1.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
Anarchaserver is a feminist server which aim is to develop autonomous infrastructure on the Internet for feminists projects. You can find documentation about how to engage and get involved in the server in the [[Anarcha section]].&lt;br /&gt;
&lt;br /&gt;
[[File:Marina Ginesta.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== What do I need to know about wiki ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=246</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=246"/>
		<updated>2016-07-16T16:28:18Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* TransHackFeminist Convergence */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
== TransHackFeminist Convergence  ==&lt;br /&gt;
&lt;br /&gt;
The TransHackFeminist convergence is a 7 day event that was organised for the first time in Calafou (Catalonia) in August 2014. A second edition will be held from the 25 to the 31 of May in Puebla 2015 (Mexico).And 2016Third TransHackFeminist is coming https://femhack.noblogs.org/thf-2016/&lt;br /&gt;
You can find [[documentation about the THF 2014]] and about how to engage and get involved in the preparation of the [[second edition in this section]]. &lt;br /&gt;
&lt;br /&gt;
[[File:424px-8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
[[File: THF2016.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
Anarchaserver is a feminist server which aim is to develop autonomous infrastructure on the Internet for feminists projects. You can find documentation about how to engage and get involved in the server in the [[Anarcha section]].&lt;br /&gt;
&lt;br /&gt;
[[File:Marina Ginesta.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== What do I need to know about wiki ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=245</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=245"/>
		<updated>2016-07-16T16:27:42Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* TransHackFeminist Convergence */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
== TransHackFeminist Convergence  ==&lt;br /&gt;
&lt;br /&gt;
The TransHackFeminist convergence is a 7 day event that was organised for the first time in Calafou (Catalonia) in August 2014. A second edition will be held from the 25 to the 31 of May in Puebla 2015 (Mexico).And 2016Third TransHackFeminist is coming https://femhack.noblogs.org/thf-2016/&lt;br /&gt;
You can find [[documentation about the THF 2014]] and about how to engage and get involved in the preparation of the [[second edition in this section]]. &lt;br /&gt;
&lt;br /&gt;
[[File:424px-8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
[[File:http://anarchaserver.org/mediawiki/index.php/File:THF2016.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
Anarchaserver is a feminist server which aim is to develop autonomous infrastructure on the Internet for feminists projects. You can find documentation about how to engage and get involved in the server in the [[Anarcha section]].&lt;br /&gt;
&lt;br /&gt;
[[File:Marina Ginesta.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== What do I need to know about wiki ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=File:Thf1.png&amp;diff=244</id>
		<title>File:Thf1.png</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=File:Thf1.png&amp;diff=244"/>
		<updated>2016-07-16T16:25:56Z</updated>

		<summary type="html">&lt;p&gt;Thf: THF2015&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;THF2015&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=File:THF2016.png&amp;diff=243</id>
		<title>File:THF2016.png</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=File:THF2016.png&amp;diff=243"/>
		<updated>2016-07-16T16:25:00Z</updated>

		<summary type="html">&lt;p&gt;Thf: THF2016&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;THF2016&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=242</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=242"/>
		<updated>2016-07-16T16:19:36Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* TransHackFeminist Convergence */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
&lt;br /&gt;
== TransHackFeminist Convergence  ==&lt;br /&gt;
&lt;br /&gt;
The TransHackFeminist convergence is a 7 day event that was organised for the first time in Calafou (Catalonia) in August 2014. A second edition will be held from the 25 to the 31 of May in Puebla 2015 (Mexico).And 2016Third TransHackFeminist is coming https://femhack.noblogs.org/thf-2016/&lt;br /&gt;
You can find [[documentation about the THF 2014]] and about how to engage and get involved in the preparation of the [[second edition in this section]]. &lt;br /&gt;
&lt;br /&gt;
[[File:424px-8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
Anarchaserver is a feminist server which aim is to develop autonomous infrastructure on the Internet for feminists projects. You can find documentation about how to engage and get involved in the server in the [[Anarcha section]].&lt;br /&gt;
&lt;br /&gt;
[[File:Marina Ginesta.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== What do I need to know about wiki ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=230</id>
		<title>Anarcha section</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=230"/>
		<updated>2016-07-09T15:08:35Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Future is now: Milestones */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...because there is nothing more ephemeral than the digital culture...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Who was Anarcha? ====&lt;br /&gt;
&lt;br /&gt;
Anarcha was an African American slave woman. She was one of the seventy-five slaves who worked the Wescott plantation, just on the outskirts of Montgomery, Alabama.&lt;br /&gt;
&lt;br /&gt;
Anarcha went into labor one day. Three days later, she was still in labor. Dr Marion Sims was called in to assist the delivery. He writes in his autobiography that he used forceps on the fetus’s head but that he really didn’t know what he was doing since he’d had so little experience with the device. We don’t know whether the baby survived the ordeal. We do know that the mother experienced several vaginal tears from the birthing. She became incontinent afterwards due to the damage.&lt;br /&gt;
&lt;br /&gt;
A few days later, the master of the plantation sent Anarcha to Dr Sims hoping he could repair the damage to his slave, as she could not hold her bowls or bladder. As her master’s chattel, her condition reduced her value considerably.&lt;br /&gt;
&lt;br /&gt;
Sims took in the patient reluctantly. He put her up on his examination table, on her hands and knees and, using a modified pewter spoon to expand the walls of her vagina, he accidentally released the pressure that held her uterus in an awkward position. Anarcha felt immediate relief as the change in air pressure helped her uterus to relocate back into its proper position.&lt;br /&gt;
&lt;br /&gt;
Through an agreement with her master, Anarcha became Dr Sims's guinea pig. She regularly underwent surgical experiments, while positioned on Sims’s table, squatting on all fours, and fully awake without the comfort of any anesthesia. It was commonly accepted that African Americans had a higher tolerance for pain than their white counterparts. Commonly accepted but utterly wrong. &lt;br /&gt;
&lt;br /&gt;
Anarcha’s fistula (from her vaginal tears) was repaired by Sims. Sims thus became the leading expert in repairing this damage that seemed to occur in a good number of births by slave women. Though Sims was sent many slave women with fistulas, we know from his biography that he experimented repeatedly on Anarcha, as well as two other slaves, Betsy and Lucy.&lt;br /&gt;
&lt;br /&gt;
Anarcha was experimented upon, and drugged up later, not to ease her pain as much as to stifle her moans. It has been calculated that she had been operated on, perhaps, 34 times. She, Betsy, Lucy, and countless others helped Dr Sims hone his techniques and create his gynecological tools. Though on display in museums, many of Dr Sims’s tools have modern counterparts that are used today.&lt;br /&gt;
&lt;br /&gt;
Anarcha, Betsy, and Lucy left no written legacy. Slaves were forbidden to read and write, a crime punishable by death.  &lt;br /&gt;
&lt;br /&gt;
And though science today looks back on Sims’s work ambiguously, truly unsure as to his level of success, or whether he should be credited as the father of gynecology, we now know who the mothers of modern gynecology were: they were the nameless and faceless slave women upon whom Dr Sims experimented.&lt;br /&gt;
&lt;br /&gt;
Today we have just three names: Anarcha, Betsy, and Lucy. It is our hope that these names will never be. &lt;br /&gt;
&lt;br /&gt;
[http://www.mnwelldir.org/docs/history/biographies/anarcha.htm Wellness directory of Minnesota]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Why a feminist server? ====&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Feminist servers have been a topic of discussion, a partially-achieved aim and a set of slow-political practices among an informal group of transfeminists interested in creating a more autonomous infrastructure to ensure that data, projects and memory of feminist groups are properly accessible, preserved and managed.  The need for feminist servers is a response to: the unethical practices of multinational ICT companies acting as moral and hypocrite censors;  gender based online violence in the form of trolling and hateful machoists harassing feminist or women activists online and offline; the centralization of the internet and its transformation into a consumption sanctuary and a space of surveillance, control and tracking of dissent voices by government agencies among others. All these factors have led to a situation where the internet is not a safe space and where it is common to see feminist and activist work being deleted, censored, and/or prevented from being seen, heard or read. Freedom of expression is part of the feminist struggle and TransFeminists can contribute by providing collectively the knowledge and means to ensure their right to speak up remains accessible online, offline and wherever and under any format expression emerges. There will be no feminist internet without properly managed autonomous feminist servers. This is about regaining control and gaining autonomy in the access and management of our data and collective memories. It is also about being able to have feminist mailing lists, pads, wikis, content management systems, social networks and any other online services managed by feminist tech collectives. It is also of course about continuing to argue that social justice in technologically driven environments needs a more gender and culturally diverse presence in general. To achieve those objectives, many sessions during the THF discussed questions such as: what are the purposes of a Feminist Server? What  makes a server autonomous and feminist? Where are possible (socially sustainable) models for those servers? How do we create trust among us to develop cooperative approaches to the management of those spaces of resistance and transformation?&lt;br /&gt;
&lt;br /&gt;
Two feminist servers projects were rebooted during the THF!: the Systerserver [http://systerserver.net] project which was originally launched by Genderchangers and the Eclectic Tech Carnival (/etc) and which will focus on hosting online services; and this Anarchaserver which was launched by Calafou inhabitants and people involved in the organisation of the THF! and will focus on hosting data. &lt;br /&gt;
&lt;br /&gt;
Anarchaserver currently hosts a mediawiki for the documentation of the THF! and a WordPress farm. Anarchaserver is an open project, even though moderated, and we are using the THF mailing lists and an IRC channel to coordinate the several tasks that need to be achieved.&lt;br /&gt;
&lt;br /&gt;
==== Get involved ==== &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
If you want to get involved, we made different * [[Channels of communication]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Have a look at foreseen milestones below and decide what you would like to learn, contribute to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Future is now: Milestones ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
* Documentation &lt;br /&gt;
&lt;br /&gt;
What has happened in anarchaserver Aug14/Jan15? + (Stuff installed, who is admin) basically things that happened at 2013 Constant &amp;quot;Are you being Served&amp;quot; conference, during the THF2014, ESC in Graz had the Ministry of Hacking exhibitionin octiber 2014 and ?  &lt;br /&gt;
&lt;br /&gt;
**Prepare Terms of Service and Privacy documentation&lt;br /&gt;
**Prepare NekroFeministCementry (purpose, howto, zombi sites)&lt;br /&gt;
**Prepare WP farm (purpose, howto, living sites)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Accessing&lt;br /&gt;
**How to [[access server]]&lt;br /&gt;
**How to reset paswords for [[mediawiki]]&lt;br /&gt;
**How to use [[screen]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Installing/Testing hardware +distribution&lt;br /&gt;
&lt;br /&gt;
**Create [[backup]] system&lt;br /&gt;
**[[Upgrade]] debian&lt;br /&gt;
**Server [[security]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Service testing&lt;br /&gt;
&lt;br /&gt;
** Install Wordpress multifarm&lt;br /&gt;
** [[Wordpress multifarm update]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Mediagoblin for hosting/sharing files &lt;br /&gt;
*Tracktracker for follow up of activities in the server and creating tickets for bugs, requests etc&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Diffusion &lt;br /&gt;
&lt;br /&gt;
Logo, images, video design about anarchaserver&lt;br /&gt;
&lt;br /&gt;
==== Policy: Aims, working methodologies, sustainability ====&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Mediawiki&amp;diff=182</id>
		<title>Mediawiki</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Mediawiki&amp;diff=182"/>
		<updated>2015-09-20T21:05:19Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* FORGOT PASSWORD */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==FORGOT PASSWORD==&lt;br /&gt;
&lt;br /&gt;
To retrieve a password, when you know the username, you have to run a maintenance script in the folder:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cd /usr/share/mediawiki/maintenance&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
set the password for username 'example' to 'newpassword'&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;php changePassword.php --user=example --password=newpassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== CREATE USER ==&lt;br /&gt;
&lt;br /&gt;
Log in your MediaWiki and click Special Pages at the bottom left of the screen.&lt;br /&gt;
Then click Log in / create an account and create a new MediaWiki account.&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=181</id>
		<title>Anarcha section</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=181"/>
		<updated>2015-09-20T21:05:09Z</updated>

		<summary type="html">&lt;p&gt;Thf: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...because there is nothing more ephemeral than the digital culture...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Who was Anarcha? ====&lt;br /&gt;
&lt;br /&gt;
Anarcha was an African American slave woman. She was one of the seventy-five slaves who worked the Wescott plantation, just on the outskirts of Montgomery, Alabama.&lt;br /&gt;
&lt;br /&gt;
Anarcha went into labor one day. Three days later, she was still in labor. Dr Marion Sims was called in to assist the delivery. He writes in his autobiography that he used forceps on the fetus’s head but that he really didn’t know what he was doing since he’d had so little experience with the device. We don’t know whether the baby survived the ordeal. We do know that the mother experienced several vaginal tears from the birthing. She became incontinent afterwards due to the damage.&lt;br /&gt;
&lt;br /&gt;
A few days later, the master of the plantation sent Anarcha to Dr Sims hoping he could repair the damage to his slave, as she could not hold her bowls or bladder. As her master’s chattel, her condition reduced her value considerably.&lt;br /&gt;
&lt;br /&gt;
Sims took in the patient reluctantly. He put her up on his examination table, on her hands and knees and, using a modified pewter spoon to expand the walls of her vagina, he accidentally released the pressure that held her uterus in an awkward position. Anarcha felt immediate relief as the change in air pressure helped her uterus to relocate back into its proper position.&lt;br /&gt;
&lt;br /&gt;
Through an agreement with her master, Anarcha became Dr Sims's guinea pig. She regularly underwent surgical experiments, while positioned on Sims’s table, squatting on all fours, and fully awake without the comfort of any anesthesia. It was commonly accepted that African Americans had a higher tolerance for pain than their white counterparts. Commonly accepted but utterly wrong. &lt;br /&gt;
&lt;br /&gt;
Anarcha’s fistula (from her vaginal tears) was repaired by Sims. Sims thus became the leading expert in repairing this damage that seemed to occur in a good number of births by slave women. Though Sims was sent many slave women with fistulas, we know from his biography that he experimented repeatedly on Anarcha, as well as two other slaves, Betsy and Lucy.&lt;br /&gt;
&lt;br /&gt;
Anarcha was experimented upon, and drugged up later, not to ease her pain as much as to stifle her moans. It has been calculated that she had been operated on, perhaps, 34 times. She, Betsy, Lucy, and countless others helped Dr Sims hone his techniques and create his gynecological tools. Though on display in museums, many of Dr Sims’s tools have modern counterparts that are used today.&lt;br /&gt;
&lt;br /&gt;
Anarcha, Betsy, and Lucy left no written legacy. Slaves were forbidden to read and write, a crime punishable by death.  &lt;br /&gt;
&lt;br /&gt;
And though science today looks back on Sims’s work ambiguously, truly unsure as to his level of success, or whether he should be credited as the father of gynecology, we now know who the mothers of modern gynecology were: they were the nameless and faceless slave women upon whom Dr Sims experimented.&lt;br /&gt;
&lt;br /&gt;
Today we have just three names: Anarcha, Betsy, and Lucy. It is our hope that these names will never be. &lt;br /&gt;
&lt;br /&gt;
[http://www.mnwelldir.org/docs/history/biographies/anarcha.htm Wellness directory of Minnesota]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Why a feminist server? ====&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Feminist servers have been a topic of discussion, a partially-achieved aim and a set of slow-political practices among an informal group of transfeminists interested in creating a more autonomous infrastructure to ensure that data, projects and memory of feminist groups are properly accessible, preserved and managed.  The need for feminist servers is a response to: the unethical practices of multinational ICT companies acting as moral and hypocrite censors;  gender based online violence in the form of trolling and hateful machoists harassing feminist or women activists online and offline; the centralization of the internet and its transformation into a consumption sanctuary and a space of surveillance, control and tracking of dissent voices by government agencies among others. All these factors have led to a situation where the internet is not a safe space and where it is common to see feminist and activist work being deleted, censored, and/or prevented from being seen, heard or read. Freedom of expression is part of the feminist struggle and TransFeminists can contribute by providing collectively the knowledge and means to ensure their right to speak up remains accessible online, offline and wherever and under any format expression emerges. There will be no feminist internet without properly managed autonomous feminist servers. This is about regaining control and gaining autonomy in the access and management of our data and collective memories. It is also about being able to have feminist mailing lists, pads, wikis, content management systems, social networks and any other online services managed by feminist tech collectives. It is also of course about continuing to argue that social justice in technologically driven environments needs a more gender and culturally diverse presence in general. To achieve those objectives, many sessions during the THF discussed questions such as: what are the purposes of a Feminist Server? What  makes a server autonomous and feminist? Where are possible (socially sustainable) models for those servers? How do we create trust among us to develop cooperative approaches to the management of those spaces of resistance and transformation?&lt;br /&gt;
&lt;br /&gt;
Two feminist servers projects were rebooted during the THF!: the Systerserver [http://systerserver.net] project which was originally launched by Genderchangers and the Eclectic Tech Carnival (/etc) and which will focus on hosting online services; and this Anarchaserver which was launched by Calafou inhabitants and people involved in the organisation of the THF! and will focus on hosting data. &lt;br /&gt;
&lt;br /&gt;
Anarchaserver currently hosts a mediawiki for the documentation of the THF! and a WordPress farm. Anarchaserver is an open project, even though moderated, and we are using the THF mailing lists and an IRC channel to coordinate the several tasks that need to be achieved.&lt;br /&gt;
&lt;br /&gt;
==== Get involved ==== &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Join the [https://lists.riseup.net/www/info/thfeminist] mailing list which is used also for the organisation of the next THF. Present yourself to the admins and then to the list. The list is in spanglish, which means that all messages should be sent including a translation to spanish or english. &lt;br /&gt;
&lt;br /&gt;
Meet us on [http://webchat.freenode.net] the IRC chat on the channel #anarchaserver. We still have to figure out the regularity of our meetings but are leaning towards IRC chat sessions once a month and a distribution of tasks managed through the mailing list.&lt;br /&gt;
&lt;br /&gt;
Have a look at foreseen milestones below and decide what you would like to learn, contribute to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Future is now: Milestones ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
* Documentation &lt;br /&gt;
&lt;br /&gt;
What has happened in anarchaserver Aug14/Jan15? + (Stuff installed, who is admin) basically things that happened at 2013 Constant &amp;quot;Are you being Served&amp;quot; conference, during the THF2014, ESC in Graz had the Ministry of Hacking exhibitionin octiber 2014 and ?  &lt;br /&gt;
&lt;br /&gt;
Prepare Terms of Service and Privacy documentation&lt;br /&gt;
Prepare NekroFeministCementry (purpose, howto, zombi sites)&lt;br /&gt;
Prepare WP farm (purpose, howto, living sites)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Accessing&lt;br /&gt;
How to [[access server]]&lt;br /&gt;
How to reset paswords for [[mediawiki]]&lt;br /&gt;
How to use [[screen]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Installing/Testing hardware +distribution&lt;br /&gt;
&lt;br /&gt;
Create [[backup]] system&lt;br /&gt;
[[Upgrade]] debian&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Service testing&lt;br /&gt;
&lt;br /&gt;
Mediagoblin for hosting/sharing files &lt;br /&gt;
Tracktracker for follow up of activities in the server and creating tickets for bugs, requests etc&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Diffusion &lt;br /&gt;
&lt;br /&gt;
Logo, images, video design about anarchaserver&lt;br /&gt;
&lt;br /&gt;
==== Policy: Aims, working methodologies, sustainability ====&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Mediawiki&amp;diff=180</id>
		<title>Mediawiki</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Mediawiki&amp;diff=180"/>
		<updated>2015-09-20T21:03:26Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;==FORGOT PASSWORD==  To retrieve a password, when you know the username, you have to run a maintenance script in the folder:  &amp;lt;code&amp;gt;cd /usr/share/mediawiki/maintenance&amp;lt;/code&amp;gt; ...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==FORGOT PASSWORD==&lt;br /&gt;
&lt;br /&gt;
To retrieve a password, when you know the username, you have to run a maintenance script in the folder:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cd /usr/share/mediawiki/maintenance&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
set the password for username 'example' to 'newpassword'&lt;br /&gt;
&amp;lt;code&amp;gt;php changePassword.php --user=example --password=newpassword&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== CREATE USER ==&lt;br /&gt;
&lt;br /&gt;
Log in your MediaWiki and click Special Pages at the bottom left of the screen.&lt;br /&gt;
Then click Log in / create an account and create a new MediaWiki account.&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=179</id>
		<title>Anarcha section</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=179"/>
		<updated>2015-09-20T21:01:58Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Future is now: Milestones */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...because there is nothing more ephemeral than the digital culture...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Who was Anarcha? ====&lt;br /&gt;
&lt;br /&gt;
Anarcha was an African American slave woman. She was one of the seventy-five slaves who worked the Wescott plantation, just on the outskirts of Montgomery, Alabama.&lt;br /&gt;
&lt;br /&gt;
Anarcha went into labor one day. Three days later, she was still in labor. Dr Marion Sims was called in to assist the delivery. He writes in his autobiography that he used forceps on the fetus’s head but that he really didn’t know what he was doing since he’d had so little experience with the device. We don’t know whether the baby survived the ordeal. We do know that the mother experienced several vaginal tears from the birthing. She became incontinent afterwards due to the damage.&lt;br /&gt;
&lt;br /&gt;
A few days later, the master of the plantation sent Anarcha to Dr Sims hoping he could repair the damage to his slave, as she could not hold her bowls or bladder. As her master’s chattel, her condition reduced her value considerably.&lt;br /&gt;
&lt;br /&gt;
Sims took in the patient reluctantly. He put her up on his examination table, on her hands and knees and, using a modified pewter spoon to expand the walls of her vagina, he accidentally released the pressure that held her uterus in an awkward position. Anarcha felt immediate relief as the change in air pressure helped her uterus to relocate back into its proper position.&lt;br /&gt;
&lt;br /&gt;
Through an agreement with her master, Anarcha became Dr Sims's guinea pig. She regularly underwent surgical experiments, while positioned on Sims’s table, squatting on all fours, and fully awake without the comfort of any anesthesia. It was commonly accepted that African Americans had a higher tolerance for pain than their white counterparts. Commonly accepted but utterly wrong. &lt;br /&gt;
&lt;br /&gt;
Anarcha’s fistula (from her vaginal tears) was repaired by Sims. Sims thus became the leading expert in repairing this damage that seemed to occur in a good number of births by slave women. Though Sims was sent many slave women with fistulas, we know from his biography that he experimented repeatedly on Anarcha, as well as two other slaves, Betsy and Lucy.&lt;br /&gt;
&lt;br /&gt;
Anarcha was experimented upon, and drugged up later, not to ease her pain as much as to stifle her moans. It has been calculated that she had been operated on, perhaps, 34 times. She, Betsy, Lucy, and countless others helped Dr Sims hone his techniques and create his gynecological tools. Though on display in museums, many of Dr Sims’s tools have modern counterparts that are used today.&lt;br /&gt;
&lt;br /&gt;
Anarcha, Betsy, and Lucy left no written legacy. Slaves were forbidden to read and write, a crime punishable by death.  &lt;br /&gt;
&lt;br /&gt;
And though science today looks back on Sims’s work ambiguously, truly unsure as to his level of success, or whether he should be credited as the father of gynecology, we now know who the mothers of modern gynecology were: they were the nameless and faceless slave women upon whom Dr Sims experimented.&lt;br /&gt;
&lt;br /&gt;
Today we have just three names: Anarcha, Betsy, and Lucy. It is our hope that these names will never be. &lt;br /&gt;
&lt;br /&gt;
[http://www.mnwelldir.org/docs/history/biographies/anarcha.htm Wellness directory of Minnesota]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Why a feminist server? ====&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Feminist servers have been a topic of discussion, a partially-achieved aim and a set of slow-political practices among an informal group of transfeminists interested in creating a more autonomous infrastructure to ensure that data, projects and memory of feminist groups are properly accessible, preserved and managed.  The need for feminist servers is a response to: the unethical practices of multinational ICT companies acting as moral and hypocrite censors;  gender based online violence in the form of trolling and hateful machoists harassing feminist or women activists online and offline; the centralization of the internet and its transformation into a consumption sanctuary and a space of surveillance, control and tracking of dissent voices by government agencies among others. All these factors have led to a situation where the internet is not a safe space and where it is common to see feminist and activist work being deleted, censored, and/or prevented from being seen, heard or read. Freedom of expression is part of the feminist struggle and TransFeminists can contribute by providing collectively the knowledge and means to ensure their right to speak up remains accessible online, offline and wherever and under any format expression emerges. There will be no feminist internet without properly managed autonomous feminist servers. This is about regaining control and gaining autonomy in the access and management of our data and collective memories. It is also about being able to have feminist mailing lists, pads, wikis, content management systems, social networks and any other online services managed by feminist tech collectives. It is also of course about continuing to argue that social justice in technologically driven environments needs a more gender and culturally diverse presence in general. To achieve those objectives, many sessions during the THF discussed questions such as: what are the purposes of a Feminist Server? What  makes a server autonomous and feminist? Where are possible (socially sustainable) models for those servers? How do we create trust among us to develop cooperative approaches to the management of those spaces of resistance and transformation?&lt;br /&gt;
&lt;br /&gt;
Two feminist servers projects were rebooted during the THF!: the Systerserver [http://systerserver.net] project which was originally launched by Genderchangers and the Eclectic Tech Carnival (/etc) and which will focus on hosting online services; and this Anarchaserver which was launched by Calafou inhabitants and people involved in the organisation of the THF! and will focus on hosting data. &lt;br /&gt;
&lt;br /&gt;
Anarchaserver currently hosts a mediawiki for the documentation of the THF! and a WordPress farm. Anarchaserver is an open project, even though moderated, and we are using the THF mailing lists and an IRC channel to coordinate the several tasks that need to be achieved.&lt;br /&gt;
&lt;br /&gt;
==== Get involved ==== &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Join the [https://lists.riseup.net/www/info/thfeminist] mailing list which is used also for the organisation of the next THF. Present yourself to the admins and then to the list. The list is in spanglish, which means that all messages should be sent including a translation to spanish or english. &lt;br /&gt;
&lt;br /&gt;
Meet us on [http://webchat.freenode.net] the IRC chat on the channel #anarchaserver. We still have to figure out the regularity of our meetings but are leaning towards IRC chat sessions once a month and a distribution of tasks managed through the mailing list.&lt;br /&gt;
&lt;br /&gt;
Have a look at foreseen milestones below and decide what you would like to learn, contribute to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Future is now: Milestones ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
* Documentation &lt;br /&gt;
&lt;br /&gt;
What has happened in anarchaserver Aug14/Jan15? + (Stuff installed, who is admin) basically things that happened at 2013 Constant &amp;quot;Are you being Served&amp;quot; conference, during the THF2014, ESC in Graz had the Ministry of Hacking exhibitionin octiber 2014 and ?  &lt;br /&gt;
&lt;br /&gt;
-Prepare Terms of Service and Privacy documentation&lt;br /&gt;
-Prepare NekroFeministCementry (purpose, howto, zombi sites)&lt;br /&gt;
-Prepare WP farm (purpose, howto, living sites)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Accessing&lt;br /&gt;
-How to [[access server]]&lt;br /&gt;
-How to reset paswords for [[mediawiki]]&lt;br /&gt;
-How to use [[screen]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Installing/Testing hardware +distribution&lt;br /&gt;
&lt;br /&gt;
-Create [[backup]] system&lt;br /&gt;
-[[Upgrade]] debian&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Service testing&lt;br /&gt;
&lt;br /&gt;
- Mediagoblin for hosting/sharing files &lt;br /&gt;
- Tracktracker for follow up of activities in the server and creating tickets for bugs, requests etc&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Diffusion &lt;br /&gt;
&lt;br /&gt;
Logo, images, video design about anarchaserver&lt;br /&gt;
&lt;br /&gt;
==== Policy: Aims, working methodologies, sustainability ====&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=178</id>
		<title>Anarcha section</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=178"/>
		<updated>2015-09-20T20:55:30Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Future is now: Milestones */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...because there is nothing more ephemeral than the digital culture...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Who was Anarcha? ====&lt;br /&gt;
&lt;br /&gt;
Anarcha was an African American slave woman. She was one of the seventy-five slaves who worked the Wescott plantation, just on the outskirts of Montgomery, Alabama.&lt;br /&gt;
&lt;br /&gt;
Anarcha went into labor one day. Three days later, she was still in labor. Dr Marion Sims was called in to assist the delivery. He writes in his autobiography that he used forceps on the fetus’s head but that he really didn’t know what he was doing since he’d had so little experience with the device. We don’t know whether the baby survived the ordeal. We do know that the mother experienced several vaginal tears from the birthing. She became incontinent afterwards due to the damage.&lt;br /&gt;
&lt;br /&gt;
A few days later, the master of the plantation sent Anarcha to Dr Sims hoping he could repair the damage to his slave, as she could not hold her bowls or bladder. As her master’s chattel, her condition reduced her value considerably.&lt;br /&gt;
&lt;br /&gt;
Sims took in the patient reluctantly. He put her up on his examination table, on her hands and knees and, using a modified pewter spoon to expand the walls of her vagina, he accidentally released the pressure that held her uterus in an awkward position. Anarcha felt immediate relief as the change in air pressure helped her uterus to relocate back into its proper position.&lt;br /&gt;
&lt;br /&gt;
Through an agreement with her master, Anarcha became Dr Sims's guinea pig. She regularly underwent surgical experiments, while positioned on Sims’s table, squatting on all fours, and fully awake without the comfort of any anesthesia. It was commonly accepted that African Americans had a higher tolerance for pain than their white counterparts. Commonly accepted but utterly wrong. &lt;br /&gt;
&lt;br /&gt;
Anarcha’s fistula (from her vaginal tears) was repaired by Sims. Sims thus became the leading expert in repairing this damage that seemed to occur in a good number of births by slave women. Though Sims was sent many slave women with fistulas, we know from his biography that he experimented repeatedly on Anarcha, as well as two other slaves, Betsy and Lucy.&lt;br /&gt;
&lt;br /&gt;
Anarcha was experimented upon, and drugged up later, not to ease her pain as much as to stifle her moans. It has been calculated that she had been operated on, perhaps, 34 times. She, Betsy, Lucy, and countless others helped Dr Sims hone his techniques and create his gynecological tools. Though on display in museums, many of Dr Sims’s tools have modern counterparts that are used today.&lt;br /&gt;
&lt;br /&gt;
Anarcha, Betsy, and Lucy left no written legacy. Slaves were forbidden to read and write, a crime punishable by death.  &lt;br /&gt;
&lt;br /&gt;
And though science today looks back on Sims’s work ambiguously, truly unsure as to his level of success, or whether he should be credited as the father of gynecology, we now know who the mothers of modern gynecology were: they were the nameless and faceless slave women upon whom Dr Sims experimented.&lt;br /&gt;
&lt;br /&gt;
Today we have just three names: Anarcha, Betsy, and Lucy. It is our hope that these names will never be. &lt;br /&gt;
&lt;br /&gt;
[http://www.mnwelldir.org/docs/history/biographies/anarcha.htm Wellness directory of Minnesota]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Why a feminist server? ====&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Feminist servers have been a topic of discussion, a partially-achieved aim and a set of slow-political practices among an informal group of transfeminists interested in creating a more autonomous infrastructure to ensure that data, projects and memory of feminist groups are properly accessible, preserved and managed.  The need for feminist servers is a response to: the unethical practices of multinational ICT companies acting as moral and hypocrite censors;  gender based online violence in the form of trolling and hateful machoists harassing feminist or women activists online and offline; the centralization of the internet and its transformation into a consumption sanctuary and a space of surveillance, control and tracking of dissent voices by government agencies among others. All these factors have led to a situation where the internet is not a safe space and where it is common to see feminist and activist work being deleted, censored, and/or prevented from being seen, heard or read. Freedom of expression is part of the feminist struggle and TransFeminists can contribute by providing collectively the knowledge and means to ensure their right to speak up remains accessible online, offline and wherever and under any format expression emerges. There will be no feminist internet without properly managed autonomous feminist servers. This is about regaining control and gaining autonomy in the access and management of our data and collective memories. It is also about being able to have feminist mailing lists, pads, wikis, content management systems, social networks and any other online services managed by feminist tech collectives. It is also of course about continuing to argue that social justice in technologically driven environments needs a more gender and culturally diverse presence in general. To achieve those objectives, many sessions during the THF discussed questions such as: what are the purposes of a Feminist Server? What  makes a server autonomous and feminist? Where are possible (socially sustainable) models for those servers? How do we create trust among us to develop cooperative approaches to the management of those spaces of resistance and transformation?&lt;br /&gt;
&lt;br /&gt;
Two feminist servers projects were rebooted during the THF!: the Systerserver [http://systerserver.net] project which was originally launched by Genderchangers and the Eclectic Tech Carnival (/etc) and which will focus on hosting online services; and this Anarchaserver which was launched by Calafou inhabitants and people involved in the organisation of the THF! and will focus on hosting data. &lt;br /&gt;
&lt;br /&gt;
Anarchaserver currently hosts a mediawiki for the documentation of the THF! and a WordPress farm. Anarchaserver is an open project, even though moderated, and we are using the THF mailing lists and an IRC channel to coordinate the several tasks that need to be achieved.&lt;br /&gt;
&lt;br /&gt;
==== Get involved ==== &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Join the [https://lists.riseup.net/www/info/thfeminist] mailing list which is used also for the organisation of the next THF. Present yourself to the admins and then to the list. The list is in spanglish, which means that all messages should be sent including a translation to spanish or english. &lt;br /&gt;
&lt;br /&gt;
Meet us on [http://webchat.freenode.net] the IRC chat on the channel #anarchaserver. We still have to figure out the regularity of our meetings but are leaning towards IRC chat sessions once a month and a distribution of tasks managed through the mailing list.&lt;br /&gt;
&lt;br /&gt;
Have a look at foreseen milestones below and decide what you would like to learn, contribute to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Future is now: Milestones ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
* Documentation &lt;br /&gt;
&lt;br /&gt;
-What has happened in anarchaserver Aug14/Jan15? &lt;br /&gt;
&lt;br /&gt;
-(Stuff installed, who is admin) basically things that happened at 2013 Constant &amp;quot;Are you being Served&amp;quot; conference, during the THF2014, ESC in Graz had the Ministry of Hacking exhibitionin octiber 2014 and ?  &lt;br /&gt;
&lt;br /&gt;
-Prepare Terms of Service and Privacy documentation&lt;br /&gt;
&lt;br /&gt;
-Prepare NekroFeministCementry (purpose, howto, zombi sites)&lt;br /&gt;
&lt;br /&gt;
-Prepare WP farm (purpose, howto, living sites)&lt;br /&gt;
&lt;br /&gt;
* Accessing&lt;br /&gt;
-How to [[access server]]&lt;br /&gt;
-How to reset paswords for [[mediawiki]]&lt;br /&gt;
-How to use [[screen]]&lt;br /&gt;
&lt;br /&gt;
* Installing/Testing hardware +distribution&lt;br /&gt;
&lt;br /&gt;
-Create [[backup]] system&lt;br /&gt;
&lt;br /&gt;
-[[Upgrade]] debian&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Service testing&lt;br /&gt;
&lt;br /&gt;
- Mediagoblin for hosting/sharing files &lt;br /&gt;
&lt;br /&gt;
-Tracktracker for follow up of activities in the server and creating tickets for bugs, requests etc&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Diffusion &lt;br /&gt;
&lt;br /&gt;
Logo, images, video design about anarchaserver&lt;br /&gt;
&lt;br /&gt;
==== Policy: Aims, working methodologies, sustainability ====&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Upgrade&amp;diff=177</id>
		<title>Upgrade</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Upgrade&amp;diff=177"/>
		<updated>2015-09-20T20:50:33Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* STEP 3 UPDATE THE SOURCE.LIST FOR THE NEW DEBIAN RELEASE */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Upgrade debian &lt;br /&gt;
&lt;br /&gt;
==STEP 1 CHECK YOUR CURRENT DISTRIBUTION==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;nano /etc/debian-version&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
current version (sept 2015) 7.8  &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
table of reference:: table with colors&lt;br /&gt;
https://en.wikipedia.org/wiki/Debian|https://en.wikipedia.org/wiki/Debian&lt;br /&gt;
&lt;br /&gt;
check :: wheezy old stable&lt;br /&gt;
&lt;br /&gt;
==STEP 2 UPDATE CURRENT DISTRIBUTION==&lt;br /&gt;
old stable &amp;gt; to stable&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;apt-get update &amp;amp;&amp;amp; apt-get dist-upgrade &amp;amp;&amp;amp; dist-upgrade &amp;amp;&amp;amp; apt-get autoremove&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(first update than upgrade, than upgrade again if something didn't happen well and autoremove the packages which are not used)&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
the first command update doesn't work, it logs that we failed to connect to archive.debian.org, a person who is in a paralelle working session, encountered this problem before and know the actual state of the vps where our vps is hosted, he was informed about a case of ddos attacks because of websiteon abortion, so we need to resolve our dns and have another nameserver.. or at least figure out the right numbers&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==STEP 3 UPDATE THE SOURCE.LIST FOR THE NEW DEBIAN RELEASE==&lt;br /&gt;
update the source.list&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;nano /etc/apt/sources.list&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
wikipedia / debian &amp;gt; table with colors&amp;lt;br /&amp;gt;&lt;br /&gt;
(change the name of the distribution)&lt;br /&gt;
&lt;br /&gt;
https://wiki.debian.org/SourcesList|https://wiki.debian.org/SourcesList&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;deb http://www.debian.org/debian jessie main&amp;lt;/code&amp;gt;&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;deb-src http://www.debian.org/debian jessie main&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==STEP 4 UPGRADE==&lt;br /&gt;
&amp;lt;code&amp;gt;apt-get update &amp;amp;&amp;amp; apt-get dist-upgrade &amp;amp;&amp;amp; dist-upgrade &amp;amp;&amp;amp; apt-get autoremove&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Upgrade&amp;diff=176</id>
		<title>Upgrade</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Upgrade&amp;diff=176"/>
		<updated>2015-09-20T20:44:09Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* STEP 2 UPDATE CURRENT DISTRIBUTION */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Upgrade debian &lt;br /&gt;
&lt;br /&gt;
==STEP 1 CHECK YOUR CURRENT DISTRIBUTION==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;nano /etc/debian-version&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
current version (sept 2015) 7.8  &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
table of reference:: table with colors&lt;br /&gt;
https://en.wikipedia.org/wiki/Debian|https://en.wikipedia.org/wiki/Debian&lt;br /&gt;
&lt;br /&gt;
check :: wheezy old stable&lt;br /&gt;
&lt;br /&gt;
==STEP 2 UPDATE CURRENT DISTRIBUTION==&lt;br /&gt;
old stable &amp;gt; to stable&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;apt-get update &amp;amp;&amp;amp; apt-get dist-upgrade &amp;amp;&amp;amp; dist-upgrade &amp;amp;&amp;amp; apt-get autoremove&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(first update than upgrade, than upgrade again if something didn't happen well and autoremove the packages which are not used)&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
the first command update doesn't work, it logs that we failed to connect to archive.debian.org, a person who is in a paralelle working session, encountered this problem before and know the actual state of the vps where our vps is hosted, he was informed about a case of ddos attacks because of websiteon abortion, so we need to resolve our dns and have another nameserver.. or at least figure out the right numbers&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==STEP 3 UPDATE THE SOURCE.LIST FOR THE NEW DEBIAN RELEASE==&lt;br /&gt;
update the source.list&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;nano /etc/apt/sources.list&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
wikipedia / debian &amp;gt; table with colors&amp;lt;br /&amp;gt;&lt;br /&gt;
(change the name of the distribution)&lt;br /&gt;
&lt;br /&gt;
https://wiki.debian.org/SourcesList|https://wiki.debian.org/SourcesList&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;deb http://www.debian.org/debian jessie main&amp;lt;/code&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;deb-src http://www.debian.org/debian jessie main&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==STEP 4 UPGRADE==&lt;br /&gt;
&amp;lt;code&amp;gt;apt-get update &amp;amp;&amp;amp; apt-get dist-upgrade &amp;amp;&amp;amp; dist-upgrade &amp;amp;&amp;amp; apt-get autoremove&amp;lt;/code&amp;gt;&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=175</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=175"/>
		<updated>2015-09-20T20:40:08Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* How to Get started with the wiki */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Welcome to the Wiki of the TransHackFeminist convergence and the AnarchaServer. Both projects even if related and sharing common spaces are also different in their purposes. &lt;br /&gt;
&lt;br /&gt;
== TransHackFeminist Convergence  ==&lt;br /&gt;
&lt;br /&gt;
The TransHackFeminist convergence is a 7 day event that was organised for the first time in Calafou (Catalonia) in August 2014. A second edition will be held from the 25 to the 31 of May in Puebla 2015 (Mexico).&lt;br /&gt;
You can find [[documentation about the THF 2014]] and about how to engage and get involved in the preparation of the [[second edition in this section]]. &lt;br /&gt;
&lt;br /&gt;
[[File:424px-8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
Anarchaserver is a feminist server which aim is to develop autonomous infrastructure on the Internet for feminists projects. You can find documentation about how to engage and get involved in the server in the [[Anarcha section]].&lt;br /&gt;
&lt;br /&gt;
[[File:Marina Ginesta.png]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== What do I need to know about wiki ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=149</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=149"/>
		<updated>2015-08-13T22:02:43Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* creating .ssh directory and authorized_keys document in the superuser home directory */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair. When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The public key we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
===== Send public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard or send it by email.&lt;br /&gt;
&lt;br /&gt;
=== creating new sysadmin accounts ===&lt;br /&gt;
&lt;br /&gt;
'''Changing to root user'''&lt;br /&gt;
$ su root&lt;br /&gt;
&lt;br /&gt;
'''we create superuser''' &lt;br /&gt;
$ adduser superusername&lt;br /&gt;
	&lt;br /&gt;
'''add the superuser to the group sudoers'''&lt;br /&gt;
$ sudo addgroup (username)  sudoers&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
$ mkdir .ssh&lt;br /&gt;
$ chmod 700 .ssh&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
$ nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
$ chmod 600 .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now the new sysadmin may SSH login as your new user, using the private key as authentication.&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=148</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=148"/>
		<updated>2015-08-13T22:02:28Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* creating .ssh directory and authorized_keys document in the superuser home directory */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair. When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The public key we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
===== Send public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard or send it by email.&lt;br /&gt;
&lt;br /&gt;
=== creating new sysadmin accounts ===&lt;br /&gt;
&lt;br /&gt;
'''Changing to root user'''&lt;br /&gt;
$ su root&lt;br /&gt;
&lt;br /&gt;
'''we create superuser''' &lt;br /&gt;
$ adduser superusername&lt;br /&gt;
	&lt;br /&gt;
'''add the superuser to the group sudoers'''&lt;br /&gt;
$ sudo addgroup (username)  sudoers&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
$ mkdir .ssh&lt;br /&gt;
$ chmod 700 .ssh&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
$ nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
$ chmod 600 .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Now the new sysadmin may SSH login as your new user, using the private key as authentication.&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=147</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=147"/>
		<updated>2015-08-13T22:00:19Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* creating new sysadmin accounts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair. When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The public key we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
===== Send public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard or send it by email.&lt;br /&gt;
&lt;br /&gt;
=== creating new sysadmin accounts ===&lt;br /&gt;
&lt;br /&gt;
'''Changing to root user'''&lt;br /&gt;
$ su root&lt;br /&gt;
&lt;br /&gt;
'''we create superuser''' &lt;br /&gt;
$ adduser superusername&lt;br /&gt;
	&lt;br /&gt;
'''add the superuser to the group sudoers'''&lt;br /&gt;
$ sudo addgroup (username)  sudoers&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=146</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=146"/>
		<updated>2015-08-13T22:00:03Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* creating new sysadmin accounts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair. When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The public key we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
===== Send public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard or send it by email.&lt;br /&gt;
&lt;br /&gt;
=== creating new sysadmin accounts ===&lt;br /&gt;
'''Changing to root user'''&lt;br /&gt;
$ su root&lt;br /&gt;
&lt;br /&gt;
'''we create superuser''' &lt;br /&gt;
$ adduser superusername&lt;br /&gt;
	&lt;br /&gt;
'''add the superuser to the group sudoers'''&lt;br /&gt;
$ sudo addgroup (username)  sudoers&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=145</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=145"/>
		<updated>2015-08-13T21:59:31Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* creating super user accounts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair. When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The public key we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
===== Send public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard or send it by email.&lt;br /&gt;
&lt;br /&gt;
=== creating new sysadmin accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
$ su root&lt;br /&gt;
&lt;br /&gt;
we create superuser &lt;br /&gt;
$ adduser superusername&lt;br /&gt;
	&lt;br /&gt;
add the superuser to the group sudoers:&lt;br /&gt;
$ sudo addgroup (username)  sudoers&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=144</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=144"/>
		<updated>2015-08-13T21:56:58Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Copy public key to the server */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair. When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The public key we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
===== Send public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard or send it by email.&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=143</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=143"/>
		<updated>2015-08-13T21:55:38Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Create RSA Key Pair */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair. When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The public key we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
===== Copy public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard.&lt;br /&gt;
&lt;br /&gt;
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory of the directory. Assuming that we are going to create superuser accounts for each new admin we will do the following:&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=142</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=142"/>
		<updated>2015-08-13T21:54:44Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Create RSA Key Pair */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair: &lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in ~/.ssh, a public key and a private key. The publickey we will send to an admin of Anarcha server.&lt;br /&gt;
&lt;br /&gt;
When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
===== Copy public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard.&lt;br /&gt;
&lt;br /&gt;
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory of the directory. Assuming that we are going to create superuser accounts for each new admin we will do the following:&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=141</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=141"/>
		<updated>2015-08-13T21:54:14Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Create RSA Key Pair */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create the rsa key pair in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if trying to login from a different user, it will not work&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair: &lt;br /&gt;
&lt;br /&gt;
	$ ssh-keygen&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in [[~/.ssh,]] a public key and a private key. The publickey we will send to an admin of Anarcha server.&lt;br /&gt;
email:&lt;br /&gt;
&lt;br /&gt;
When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
===== Copy public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard.&lt;br /&gt;
&lt;br /&gt;
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory of the directory. Assuming that we are going to create superuser accounts for each new admin we will do the following:&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=140</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=140"/>
		<updated>2015-08-13T21:51:32Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Debug */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server. I can use this key pair for several servers, but if I want to enter a same server from different computers, I create different rsa key pairs.&lt;br /&gt;
Lo voy a crear a nivel local (en mi compu) y esa va a ser la llave rsa ssh que voy a usar para entrar en mis vps. NO genero una para cada vps sino que esa misma me sirve para todas. Si voy a usar varios ordenadores para entrar en un vps, sí necesitaré crear una llave ssh por máquina desde la cual estoy accediendo.&lt;br /&gt;
&lt;br /&gt;
So each admin in a server is going to have at least one rsa key pair.&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create this in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if Im trying to login from a different user, it will confuse home directories since each user has a different home directory.&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair: &lt;br /&gt;
&lt;br /&gt;
	$ **ssh-keygen**&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in [[~/.ssh,]] a public key and a private key. We are going to copy our private key to the server. If we dont have access to this server, we will send it to the admin so that she can do it.&lt;br /&gt;
&lt;br /&gt;
When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
===== Copy public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard.&lt;br /&gt;
&lt;br /&gt;
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory of the directory. Assuming that we are going to create superuser accounts for each new admin we will do the following:&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=139</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=139"/>
		<updated>2015-08-13T21:51:20Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Making changes in ssh */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Debug =====&lt;br /&gt;
with -v flag. max 3 &amp;quot;v&amp;quot;s&lt;br /&gt;
ssh [[user@server]]  -vvv&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server. I can use this key pair for several servers, but if I want to enter a same server from different computers, I create different rsa key pairs.&lt;br /&gt;
Lo voy a crear a nivel local (en mi compu) y esa va a ser la llave rsa ssh que voy a usar para entrar en mis vps. NO genero una para cada vps sino que esa misma me sirve para todas. Si voy a usar varios ordenadores para entrar en un vps, sí necesitaré crear una llave ssh por máquina desde la cual estoy accediendo.&lt;br /&gt;
&lt;br /&gt;
So each admin in a server is going to have at least one rsa key pair.&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create this in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if Im trying to login from a different user, it will confuse home directories since each user has a different home directory.&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair: &lt;br /&gt;
&lt;br /&gt;
	$ **ssh-keygen**&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in [[~/.ssh,]] a public key and a private key. We are going to copy our private key to the server. If we dont have access to this server, we will send it to the admin so that she can do it.&lt;br /&gt;
&lt;br /&gt;
When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
===== Copy public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard.&lt;br /&gt;
&lt;br /&gt;
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory of the directory. Assuming that we are going to create superuser accounts for each new admin we will do the following:&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=138</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=138"/>
		<updated>2015-08-13T21:50:28Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* SSH */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone.  Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on the server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
===== Making changes in ssh =====&lt;br /&gt;
&lt;br /&gt;
Remember to:&lt;br /&gt;
&lt;br /&gt;
	**sudo /etc/init.d/ssh restart**&lt;br /&gt;
&lt;br /&gt;
Tip: I can check all available services in /etc/init.d&lt;br /&gt;
&lt;br /&gt;
Attention: if theres problems, grep to see if it actually stops the service&lt;br /&gt;
Like this:&lt;br /&gt;
	**sudo /etc/init.d/ssh stop**&lt;br /&gt;
        ps aux | grep ssh&lt;br /&gt;
	**sudo /etc/init.d/ssh start**&lt;br /&gt;
        ps aux | grep ssh&lt;br /&gt;
&lt;br /&gt;
===== Debug =====&lt;br /&gt;
with -v flag. max 3 &amp;quot;v&amp;quot;s&lt;br /&gt;
ssh [[user@server]]  -vvv&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server. I can use this key pair for several servers, but if I want to enter a same server from different computers, I create different rsa key pairs.&lt;br /&gt;
Lo voy a crear a nivel local (en mi compu) y esa va a ser la llave rsa ssh que voy a usar para entrar en mis vps. NO genero una para cada vps sino que esa misma me sirve para todas. Si voy a usar varios ordenadores para entrar en un vps, sí necesitaré crear una llave ssh por máquina desde la cual estoy accediendo.&lt;br /&gt;
&lt;br /&gt;
So each admin in a server is going to have at least one rsa key pair.&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create this in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if Im trying to login from a different user, it will confuse home directories since each user has a different home directory.&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair: &lt;br /&gt;
&lt;br /&gt;
	$ **ssh-keygen**&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in [[~/.ssh,]] a public key and a private key. We are going to copy our private key to the server. If we dont have access to this server, we will send it to the admin so that she can do it.&lt;br /&gt;
&lt;br /&gt;
When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
===== Copy public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard.&lt;br /&gt;
&lt;br /&gt;
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory of the directory. Assuming that we are going to create superuser accounts for each new admin we will do the following:&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=137</id>
		<title>Access server</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Access_server&amp;diff=137"/>
		<updated>2015-08-13T21:18:54Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot; ====== SSH ======   SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone. While a password can eventually be c...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
====== SSH ======&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SSH keys provide **a more secure way** of logging into a virtual private server with SSH than using a password alone. While a password can eventually be cracked with a brute force attack, SSH keys are nearly impossible to decipher by brute force alone. Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on any server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Making changes in ssh =====&lt;br /&gt;
&lt;br /&gt;
Remember to:&lt;br /&gt;
&lt;br /&gt;
	**sudo /etc/init.d/ssh restart**&lt;br /&gt;
&lt;br /&gt;
Tip: I can check all available services in /etc/init.d&lt;br /&gt;
&lt;br /&gt;
Attention: if theres problems, grep to see if it actually stops the service&lt;br /&gt;
Like this:&lt;br /&gt;
	**sudo /etc/init.d/ssh stop**&lt;br /&gt;
        ps aux | grep ssh&lt;br /&gt;
	**sudo /etc/init.d/ssh start**&lt;br /&gt;
        ps aux | grep ssh&lt;br /&gt;
&lt;br /&gt;
===== Debug =====&lt;br /&gt;
with -v flag. max 3 &amp;quot;v&amp;quot;s&lt;br /&gt;
ssh [[user@server]]  -vvv&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Create RSA Key Pair =====&lt;br /&gt;
You create your rsa key pair in the computer you want to log to the server. I can use this key pair for several servers, but if I want to enter a same server from different computers, I create different rsa key pairs.&lt;br /&gt;
Lo voy a crear a nivel local (en mi compu) y esa va a ser la llave rsa ssh que voy a usar para entrar en mis vps. NO genero una para cada vps sino que esa misma me sirve para todas. Si voy a usar varios ordenadores para entrar en un vps, sí necesitaré crear una llave ssh por máquina desde la cual estoy accediendo.&lt;br /&gt;
&lt;br /&gt;
So each admin in a server is going to have at least one rsa key pair.&lt;br /&gt;
&lt;br /&gt;
Be careful to pay attention from which user you create this in your local machine (computer). Since the rsa key pairs are saved in a hidden directory in my user home directory (~/.ssh), if Im trying to login from a different user, it will confuse home directories since each user has a different home directory.&lt;br /&gt;
&lt;br /&gt;
So, from the user in my localmachine that I wish to use to access the server, I will create my rsa key pair: &lt;br /&gt;
&lt;br /&gt;
	$ **ssh-keygen**&lt;br /&gt;
&lt;br /&gt;
By default it will generate two keys in [[~/.ssh,]] a public key and a private key. We are going to copy our private key to the server. If we dont have access to this server, we will send it to the admin so that she can do it.&lt;br /&gt;
&lt;br /&gt;
When generating the key, you will need to introduce a **&amp;quot;passphrase&amp;quot;.**&lt;br /&gt;
&lt;br /&gt;
===== Copy public key to the server =====&lt;br /&gt;
&lt;br /&gt;
After generating an SSH key pair, you will want to copy your public key to your new server.&lt;br /&gt;
&lt;br /&gt;
Assuming you generated an SSH key pair using the previous step, use the following command at the terminal of your local machine to print your public key (id_rsa.pub):&lt;br /&gt;
&lt;br /&gt;
	**cat ~/.ssh/id_rsa.pub**&lt;br /&gt;
&lt;br /&gt;
This should print your public SSH key, which should look something like the following:&lt;br /&gt;
&lt;br /&gt;
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDBGTO0tsVejssuaYR5R3Y/i73SppJAhme1dH7W2c47d4gOqB4izP0+fRLfvbz/tnXFz4iOP/H6eCV05hqUhF+KYRxt9Y8tVMrpDZR2l75o6+xSbUOMu6xN+uVF0T9XzKcxmzTmnV7Na5up3QM3DoSRYX/EP3utr2+zAqpJIfKPLdA74w7g56oYWI9blpnpzxkEd3edVJOivUkpZ4JoenWManvIaSdMTJXMy3MtlQhva+j9CgguyVbUkdzK9KKEuah+pFZvaugtebsU+bllPTB0nlXGIJk98Ie9ZtxuY3nCKneB+KjKiXrAvXUPCI9mWkYS/1rggpFmu3HbXBnWSUdf localuser@machine.local&lt;br /&gt;
&lt;br /&gt;
Select the public key, and copy it to your clipboard.&lt;br /&gt;
&lt;br /&gt;
To enable the use of SSH key to authenticate as the new remote user, you must add the public key to a special file in the user's home directory of the directory. Assuming that we are going to create superuser accounts for each new admin we will do the following:&lt;br /&gt;
&lt;br /&gt;
=== creating super user accounts ===&lt;br /&gt;
Changing to root user&lt;br /&gt;
	su root&lt;br /&gt;
&lt;br /&gt;
we create superuser (note: it will ask me to introduce a passwd)&lt;br /&gt;
	adduser superusername&lt;br /&gt;
	&lt;br /&gt;
then we will add the superuser to sudoers:&lt;br /&gt;
	gpasswd -a superusername sudo&lt;br /&gt;
&lt;br /&gt;
we now change to superuser:&lt;br /&gt;
	su superuser&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When we change user, we will be by default in the  user's home directory (~). You can do &amp;quot;cd ~&amp;quot; just in case.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== creating .ssh directory and authorized_keys document in the superuser home directory ===&lt;br /&gt;
&lt;br /&gt;
As the superuser to whom we want to give ssh access to the server, create a new directory called .ssh and restrict its permissions with the following commands:&lt;br /&gt;
&lt;br /&gt;
	**mkdir .ssh**&lt;br /&gt;
	**chmod 700 .ssh**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Now open a file in .ssh called authorized_keys with a text editor. We will use nano to edit the file:&lt;br /&gt;
&lt;br /&gt;
	**nano .ssh/authorized_keys**&lt;br /&gt;
&lt;br /&gt;
Now copy-paste the public key (which should be in your clipboard) by pasting it into the editor.&lt;br /&gt;
&lt;br /&gt;
Save and close.&lt;br /&gt;
&lt;br /&gt;
Now restrict the permissions of the authorized_keys file with this command:&lt;br /&gt;
&lt;br /&gt;
	**chmod 600 .ssh/authorized_keys**&lt;br /&gt;
        chown [[superuser:group]]&lt;br /&gt;
&lt;br /&gt;
Type this command once to return to the root user:&lt;br /&gt;
&lt;br /&gt;
exit&lt;br /&gt;
&lt;br /&gt;
Now you may SSH login as your new user, using the private key as authentication.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SSH Reverse DNS Lookup Disable =====&lt;br /&gt;
The invalid logins are normal, since there are bots that try to bruteforce servers.&lt;br /&gt;
&lt;br /&gt;
As for the &amp;quot;possible break-in attempt&amp;quot; message, The system is trying to do a reverse DNS lookup to match the connecting IP with the hostname that is trying to connect and fails to do so.&lt;br /&gt;
&lt;br /&gt;
The setting that controls that is &amp;quot;UseDNS&amp;quot; in /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
sudo nano [[/etc/ssh/sshd_config]]&lt;br /&gt;
&lt;br /&gt;
y agrega la línea:&lt;br /&gt;
&lt;br /&gt;
UseDNS no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Force ssh login to server =====&lt;br /&gt;
&lt;br /&gt;
	**sudo nano /etc/ssh/sshd_config**&lt;br /&gt;
&lt;br /&gt;
and change:&lt;br /&gt;
&lt;br /&gt;
ChallengeResponseAuthentication no&lt;br /&gt;
PasswordAuthentication no&lt;br /&gt;
UsePAM yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
sudo /etc/init.d/ssh restart&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Change ssh port access =====&lt;br /&gt;
&lt;br /&gt;
sudo nano /etc/ssh/sshd_config&lt;br /&gt;
&lt;br /&gt;
The first option that you may want to change is the port that SSH runs on. Find the line that looks like this:&lt;br /&gt;
&lt;br /&gt;
Port 22&lt;br /&gt;
&lt;br /&gt;
If we change this number to something in **between 1025 and 65536**, the SSH service on our server will look for connections on a different port. This is sometimes helpful because unauthorized users sometimes try to break into servers by attacking SSH. If you change the location, they will need to complete the extra step of sniffing it out.&lt;br /&gt;
&lt;br /&gt;
If you change this value, you will need to keep in mind that your server is running on the new port.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
**service ssh restart**&lt;br /&gt;
&lt;br /&gt;
So now you would have to access to the server like this:&lt;br /&gt;
&lt;br /&gt;
ssh superuser[[@server]] -p portnumber&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====== References ======&lt;br /&gt;
&lt;br /&gt;
http://ubuntuforums.org/showthread.php?t=1773227&lt;br /&gt;
&lt;br /&gt;
http://bodhizazen.net/Tutorials/SSH_security&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=136</id>
		<title>Anarcha section</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=136"/>
		<updated>2015-08-13T21:18:18Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Future is now: Milestones */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...because there is nothing more ephemeral than the digital culture...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Who was Anarcha? ====&lt;br /&gt;
&lt;br /&gt;
Anarcha was an African American slave woman. She was one of the seventy-five slaves who worked the Wescott plantation, just on the outskirts of Montgomery, Alabama.&lt;br /&gt;
&lt;br /&gt;
Anarcha went into labor one day. Three days later, she was still in labor. Dr Marion Sims was called in to assist the delivery. He writes in his autobiography that he used forceps on the fetus’s head but that he really didn’t know what he was doing since he’d had so little experience with the device. We don’t know whether the baby survived the ordeal. We do know that the mother experienced several vaginal tears from the birthing. She became incontinent afterwards due to the damage.&lt;br /&gt;
&lt;br /&gt;
A few days later, the master of the plantation sent Anarcha to Dr Sims hoping he could repair the damage to his slave, as she could not hold her bowls or bladder. As her master’s chattel, her condition reduced her value considerably.&lt;br /&gt;
&lt;br /&gt;
Sims took in the patient reluctantly. He put her up on his examination table, on her hands and knees and, using a modified pewter spoon to expand the walls of her vagina, he accidentally released the pressure that held her uterus in an awkward position. Anarcha felt immediate relief as the change in air pressure helped her uterus to relocate back into its proper position.&lt;br /&gt;
&lt;br /&gt;
Through an agreement with her master, Anarcha became Dr Sims's guinea pig. She regularly underwent surgical experiments, while positioned on Sims’s table, squatting on all fours, and fully awake without the comfort of any anesthesia. It was commonly accepted that African Americans had a higher tolerance for pain than their white counterparts. Commonly accepted but utterly wrong. &lt;br /&gt;
&lt;br /&gt;
Anarcha’s fistula (from her vaginal tears) was repaired by Sims. Sims thus became the leading expert in repairing this damage that seemed to occur in a good number of births by slave women. Though Sims was sent many slave women with fistulas, we know from his biography that he experimented repeatedly on Anarcha, as well as two other slaves, Betsy and Lucy.&lt;br /&gt;
&lt;br /&gt;
Anarcha was experimented upon, and drugged up later, not to ease her pain as much as to stifle her moans. It has been calculated that she had been operated on, perhaps, 34 times. She, Betsy, Lucy, and countless others helped Dr Sims hone his techniques and create his gynecological tools. Though on display in museums, many of Dr Sims’s tools have modern counterparts that are used today.&lt;br /&gt;
&lt;br /&gt;
Anarcha, Betsy, and Lucy left no written legacy. Slaves were forbidden to read and write, a crime punishable by death.  &lt;br /&gt;
&lt;br /&gt;
And though science today looks back on Sims’s work ambiguously, truly unsure as to his level of success, or whether he should be credited as the father of gynecology, we now know who the mothers of modern gynecology were: they were the nameless and faceless slave women upon whom Dr Sims experimented.&lt;br /&gt;
&lt;br /&gt;
Today we have just three names: Anarcha, Betsy, and Lucy. It is our hope that these names will never be. &lt;br /&gt;
&lt;br /&gt;
[http://www.mnwelldir.org/docs/history/biographies/anarcha.htm Wellness directory of Minnesota]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Why a feminist server? ====&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Feminist servers have been a topic of discussion, a partially-achieved aim and a set of slow-political practices among an informal group of transfeminists interested in creating a more autonomous infrastructure to ensure that data, projects and memory of feminist groups are properly accessible, preserved and managed.  The need for feminist servers is a response to: the unethical practices of multinational ICT companies acting as moral and hypocrite censors;  gender based online violence in the form of trolling and hateful machoists harassing feminist or women activists online and offline; the centralization of the internet and its transformation into a consumption sanctuary and a space of surveillance, control and tracking of dissent voices by government agencies among others. All these factors have led to a situation where the internet is not a safe space and where it is common to see feminist and activist work being deleted, censored, and/or prevented from being seen, heard or read. Freedom of expression is part of the feminist struggle and TransFeminists can contribute by providing collectively the knowledge and means to ensure their right to speak up remains accessible online, offline and wherever and under any format expression emerges. There will be no feminist internet without properly managed autonomous feminist servers. This is about regaining control and gaining autonomy in the access and management of our data and collective memories. It is also about being able to have feminist mailing lists, pads, wikis, content management systems, social networks and any other online services managed by feminist tech collectives. It is also of course about continuing to argue that social justice in technologically driven environments needs a more gender and culturally diverse presence in general. To achieve those objectives, many sessions during the THF discussed questions such as: what are the purposes of a Feminist Server? What  makes a server autonomous and feminist? Where are possible (socially sustainable) models for those servers? How do we create trust among us to develop cooperative approaches to the management of those spaces of resistance and transformation?&lt;br /&gt;
&lt;br /&gt;
Two feminist servers projects were rebooted during the THF!: the Systerserver [http://systerserver.net] project which was originally launched by Genderchangers and the Eclectic Tech Carnival (/etc) and which will focus on hosting online services; and this Anarchaserver which was launched by Calafou inhabitants and people involved in the organisation of the THF! and will focus on hosting data. &lt;br /&gt;
&lt;br /&gt;
Anarchaserver currently hosts a mediawiki for the documentation of the THF! and a WordPress farm. Anarchaserver is an open project, even though moderated, and we are using the THF mailing lists and an IRC channel to coordinate the several tasks that need to be achieved.&lt;br /&gt;
&lt;br /&gt;
==== Get involved ==== &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Join the [https://lists.riseup.net/www/info/thfeminist] mailing list which is used also for the organisation of the next THF. Present yourself to the admins and then to the list. The list is in spanglish, which means that all messages should be sent including a translation to spanish or english. &lt;br /&gt;
&lt;br /&gt;
Meet us on [http://webchat.freenode.net] the IRC chat on the channel #anarchaserver. We still have to figure out the regularity of our meetings but are leaning towards IRC chat sessions once a month and a distribution of tasks managed through the mailing list.&lt;br /&gt;
&lt;br /&gt;
Have a look at foreseen milestones below and decide what you would like to learn, contribute to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Future is now: Milestones ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
* Documentation &lt;br /&gt;
&lt;br /&gt;
What has happened in anarchaserver Aug14/Jan15? &lt;br /&gt;
&lt;br /&gt;
(Stuff installed, who is admin) basically things that happened at 2013 Constant &amp;quot;Are you being Served&amp;quot; conference, during the THF2014, ESC in Graz had the Ministry of Hacking exhibitionin octiber 2014 and ?  &lt;br /&gt;
&lt;br /&gt;
Prepare Terms of Service and Privacy documentation&lt;br /&gt;
&lt;br /&gt;
Prepare NekroFeministCementry (purpose, howto, zombi sites)&lt;br /&gt;
&lt;br /&gt;
Prepare WP farm (purpose, howto, living sites)&lt;br /&gt;
&lt;br /&gt;
* Accessing&lt;br /&gt;
How to [[access server]]&lt;br /&gt;
&lt;br /&gt;
* Intalling/Testing&lt;br /&gt;
&lt;br /&gt;
Mediagoblin for hosting/sharing files &lt;br /&gt;
&lt;br /&gt;
Tracktracker for follow up of activities in the server and creating tickets for bugs, requests etc&lt;br /&gt;
&lt;br /&gt;
Word press farm testing &lt;br /&gt;
&lt;br /&gt;
* Diffusion &lt;br /&gt;
&lt;br /&gt;
Logo, images, video design about anarchaserver&lt;br /&gt;
&lt;br /&gt;
==== Policy: Aims, working methodologies, sustainability ====&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=134</id>
		<title>Anarcha section</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=134"/>
		<updated>2015-08-13T21:17:06Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Future is now: Milestones */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...because there is nothing more ephemeral than the digital culture...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Who was Anarcha? ====&lt;br /&gt;
&lt;br /&gt;
Anarcha was an African American slave woman. She was one of the seventy-five slaves who worked the Wescott plantation, just on the outskirts of Montgomery, Alabama.&lt;br /&gt;
&lt;br /&gt;
Anarcha went into labor one day. Three days later, she was still in labor. Dr Marion Sims was called in to assist the delivery. He writes in his autobiography that he used forceps on the fetus’s head but that he really didn’t know what he was doing since he’d had so little experience with the device. We don’t know whether the baby survived the ordeal. We do know that the mother experienced several vaginal tears from the birthing. She became incontinent afterwards due to the damage.&lt;br /&gt;
&lt;br /&gt;
A few days later, the master of the plantation sent Anarcha to Dr Sims hoping he could repair the damage to his slave, as she could not hold her bowls or bladder. As her master’s chattel, her condition reduced her value considerably.&lt;br /&gt;
&lt;br /&gt;
Sims took in the patient reluctantly. He put her up on his examination table, on her hands and knees and, using a modified pewter spoon to expand the walls of her vagina, he accidentally released the pressure that held her uterus in an awkward position. Anarcha felt immediate relief as the change in air pressure helped her uterus to relocate back into its proper position.&lt;br /&gt;
&lt;br /&gt;
Through an agreement with her master, Anarcha became Dr Sims's guinea pig. She regularly underwent surgical experiments, while positioned on Sims’s table, squatting on all fours, and fully awake without the comfort of any anesthesia. It was commonly accepted that African Americans had a higher tolerance for pain than their white counterparts. Commonly accepted but utterly wrong. &lt;br /&gt;
&lt;br /&gt;
Anarcha’s fistula (from her vaginal tears) was repaired by Sims. Sims thus became the leading expert in repairing this damage that seemed to occur in a good number of births by slave women. Though Sims was sent many slave women with fistulas, we know from his biography that he experimented repeatedly on Anarcha, as well as two other slaves, Betsy and Lucy.&lt;br /&gt;
&lt;br /&gt;
Anarcha was experimented upon, and drugged up later, not to ease her pain as much as to stifle her moans. It has been calculated that she had been operated on, perhaps, 34 times. She, Betsy, Lucy, and countless others helped Dr Sims hone his techniques and create his gynecological tools. Though on display in museums, many of Dr Sims’s tools have modern counterparts that are used today.&lt;br /&gt;
&lt;br /&gt;
Anarcha, Betsy, and Lucy left no written legacy. Slaves were forbidden to read and write, a crime punishable by death.  &lt;br /&gt;
&lt;br /&gt;
And though science today looks back on Sims’s work ambiguously, truly unsure as to his level of success, or whether he should be credited as the father of gynecology, we now know who the mothers of modern gynecology were: they were the nameless and faceless slave women upon whom Dr Sims experimented.&lt;br /&gt;
&lt;br /&gt;
Today we have just three names: Anarcha, Betsy, and Lucy. It is our hope that these names will never be. &lt;br /&gt;
&lt;br /&gt;
[http://www.mnwelldir.org/docs/history/biographies/anarcha.htm Wellness directory of Minnesota]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Why a feminist server? ====&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Feminist servers have been a topic of discussion, a partially-achieved aim and a set of slow-political practices among an informal group of transfeminists interested in creating a more autonomous infrastructure to ensure that data, projects and memory of feminist groups are properly accessible, preserved and managed.  The need for feminist servers is a response to: the unethical practices of multinational ICT companies acting as moral and hypocrite censors;  gender based online violence in the form of trolling and hateful machoists harassing feminist or women activists online and offline; the centralization of the internet and its transformation into a consumption sanctuary and a space of surveillance, control and tracking of dissent voices by government agencies among others. All these factors have led to a situation where the internet is not a safe space and where it is common to see feminist and activist work being deleted, censored, and/or prevented from being seen, heard or read. Freedom of expression is part of the feminist struggle and TransFeminists can contribute by providing collectively the knowledge and means to ensure their right to speak up remains accessible online, offline and wherever and under any format expression emerges. There will be no feminist internet without properly managed autonomous feminist servers. This is about regaining control and gaining autonomy in the access and management of our data and collective memories. It is also about being able to have feminist mailing lists, pads, wikis, content management systems, social networks and any other online services managed by feminist tech collectives. It is also of course about continuing to argue that social justice in technologically driven environments needs a more gender and culturally diverse presence in general. To achieve those objectives, many sessions during the THF discussed questions such as: what are the purposes of a Feminist Server? What  makes a server autonomous and feminist? Where are possible (socially sustainable) models for those servers? How do we create trust among us to develop cooperative approaches to the management of those spaces of resistance and transformation?&lt;br /&gt;
&lt;br /&gt;
Two feminist servers projects were rebooted during the THF!: the Systerserver [http://systerserver.net] project which was originally launched by Genderchangers and the Eclectic Tech Carnival (/etc) and which will focus on hosting online services; and this Anarchaserver which was launched by Calafou inhabitants and people involved in the organisation of the THF! and will focus on hosting data. &lt;br /&gt;
&lt;br /&gt;
Anarchaserver currently hosts a mediawiki for the documentation of the THF! and a WordPress farm. Anarchaserver is an open project, even though moderated, and we are using the THF mailing lists and an IRC channel to coordinate the several tasks that need to be achieved.&lt;br /&gt;
&lt;br /&gt;
==== Get involved ==== &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Join the [https://lists.riseup.net/www/info/thfeminist] mailing list which is used also for the organisation of the next THF. Present yourself to the admins and then to the list. The list is in spanglish, which means that all messages should be sent including a translation to spanish or english. &lt;br /&gt;
&lt;br /&gt;
Meet us on [http://webchat.freenode.net] the IRC chat on the channel #anarchaserver. We still have to figure out the regularity of our meetings but are leaning towards IRC chat sessions once a month and a distribution of tasks managed through the mailing list.&lt;br /&gt;
&lt;br /&gt;
Have a look at foreseen milestones below and decide what you would like to learn, contribute to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Future is now: Milestones ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
* Documentation &lt;br /&gt;
&lt;br /&gt;
What has happened in anarchaserver Aug14/Jan15? &lt;br /&gt;
&lt;br /&gt;
(Stuff installed, who is admin) basically things that happened at 2013 Constant &amp;quot;Are you being Served&amp;quot; conference, during the THF2014, ESC in Graz had the Ministry of Hacking exhibitionin octiber 2014 and ?  &lt;br /&gt;
&lt;br /&gt;
Prepare Terms of Service and Privacy documentation&lt;br /&gt;
&lt;br /&gt;
Prepare NekroFeministCementry (purpose, howto, zombi sites)&lt;br /&gt;
&lt;br /&gt;
Prepare WP farm (purpose, howto, living sites)&lt;br /&gt;
&lt;br /&gt;
* Accessing&lt;br /&gt;
How to access the [[Server]]&lt;br /&gt;
&lt;br /&gt;
* Intalling/Testing&lt;br /&gt;
&lt;br /&gt;
Mediagoblin for hosting/sharing files &lt;br /&gt;
&lt;br /&gt;
Tracktracker for follow up of activities in the server and creating tickets for bugs, requests etc&lt;br /&gt;
&lt;br /&gt;
Word press farm testing &lt;br /&gt;
&lt;br /&gt;
* Diffusion &lt;br /&gt;
&lt;br /&gt;
Logo, images, video design about anarchaserver&lt;br /&gt;
&lt;br /&gt;
==== Policy: Aims, working methodologies, sustainability ====&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=133</id>
		<title>Anarcha section</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Anarcha_section&amp;diff=133"/>
		<updated>2015-08-13T21:15:57Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Future is now: Milestones */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;...because there is nothing more ephemeral than the digital culture...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Who was Anarcha? ====&lt;br /&gt;
&lt;br /&gt;
Anarcha was an African American slave woman. She was one of the seventy-five slaves who worked the Wescott plantation, just on the outskirts of Montgomery, Alabama.&lt;br /&gt;
&lt;br /&gt;
Anarcha went into labor one day. Three days later, she was still in labor. Dr Marion Sims was called in to assist the delivery. He writes in his autobiography that he used forceps on the fetus’s head but that he really didn’t know what he was doing since he’d had so little experience with the device. We don’t know whether the baby survived the ordeal. We do know that the mother experienced several vaginal tears from the birthing. She became incontinent afterwards due to the damage.&lt;br /&gt;
&lt;br /&gt;
A few days later, the master of the plantation sent Anarcha to Dr Sims hoping he could repair the damage to his slave, as she could not hold her bowls or bladder. As her master’s chattel, her condition reduced her value considerably.&lt;br /&gt;
&lt;br /&gt;
Sims took in the patient reluctantly. He put her up on his examination table, on her hands and knees and, using a modified pewter spoon to expand the walls of her vagina, he accidentally released the pressure that held her uterus in an awkward position. Anarcha felt immediate relief as the change in air pressure helped her uterus to relocate back into its proper position.&lt;br /&gt;
&lt;br /&gt;
Through an agreement with her master, Anarcha became Dr Sims's guinea pig. She regularly underwent surgical experiments, while positioned on Sims’s table, squatting on all fours, and fully awake without the comfort of any anesthesia. It was commonly accepted that African Americans had a higher tolerance for pain than their white counterparts. Commonly accepted but utterly wrong. &lt;br /&gt;
&lt;br /&gt;
Anarcha’s fistula (from her vaginal tears) was repaired by Sims. Sims thus became the leading expert in repairing this damage that seemed to occur in a good number of births by slave women. Though Sims was sent many slave women with fistulas, we know from his biography that he experimented repeatedly on Anarcha, as well as two other slaves, Betsy and Lucy.&lt;br /&gt;
&lt;br /&gt;
Anarcha was experimented upon, and drugged up later, not to ease her pain as much as to stifle her moans. It has been calculated that she had been operated on, perhaps, 34 times. She, Betsy, Lucy, and countless others helped Dr Sims hone his techniques and create his gynecological tools. Though on display in museums, many of Dr Sims’s tools have modern counterparts that are used today.&lt;br /&gt;
&lt;br /&gt;
Anarcha, Betsy, and Lucy left no written legacy. Slaves were forbidden to read and write, a crime punishable by death.  &lt;br /&gt;
&lt;br /&gt;
And though science today looks back on Sims’s work ambiguously, truly unsure as to his level of success, or whether he should be credited as the father of gynecology, we now know who the mothers of modern gynecology were: they were the nameless and faceless slave women upon whom Dr Sims experimented.&lt;br /&gt;
&lt;br /&gt;
Today we have just three names: Anarcha, Betsy, and Lucy. It is our hope that these names will never be. &lt;br /&gt;
&lt;br /&gt;
[http://www.mnwelldir.org/docs/history/biographies/anarcha.htm Wellness directory of Minnesota]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Why a feminist server? ====&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Feminist servers have been a topic of discussion, a partially-achieved aim and a set of slow-political practices among an informal group of transfeminists interested in creating a more autonomous infrastructure to ensure that data, projects and memory of feminist groups are properly accessible, preserved and managed.  The need for feminist servers is a response to: the unethical practices of multinational ICT companies acting as moral and hypocrite censors;  gender based online violence in the form of trolling and hateful machoists harassing feminist or women activists online and offline; the centralization of the internet and its transformation into a consumption sanctuary and a space of surveillance, control and tracking of dissent voices by government agencies among others. All these factors have led to a situation where the internet is not a safe space and where it is common to see feminist and activist work being deleted, censored, and/or prevented from being seen, heard or read. Freedom of expression is part of the feminist struggle and TransFeminists can contribute by providing collectively the knowledge and means to ensure their right to speak up remains accessible online, offline and wherever and under any format expression emerges. There will be no feminist internet without properly managed autonomous feminist servers. This is about regaining control and gaining autonomy in the access and management of our data and collective memories. It is also about being able to have feminist mailing lists, pads, wikis, content management systems, social networks and any other online services managed by feminist tech collectives. It is also of course about continuing to argue that social justice in technologically driven environments needs a more gender and culturally diverse presence in general. To achieve those objectives, many sessions during the THF discussed questions such as: what are the purposes of a Feminist Server? What  makes a server autonomous and feminist? Where are possible (socially sustainable) models for those servers? How do we create trust among us to develop cooperative approaches to the management of those spaces of resistance and transformation?&lt;br /&gt;
&lt;br /&gt;
Two feminist servers projects were rebooted during the THF!: the Systerserver [http://systerserver.net] project which was originally launched by Genderchangers and the Eclectic Tech Carnival (/etc) and which will focus on hosting online services; and this Anarchaserver which was launched by Calafou inhabitants and people involved in the organisation of the THF! and will focus on hosting data. &lt;br /&gt;
&lt;br /&gt;
Anarchaserver currently hosts a mediawiki for the documentation of the THF! and a WordPress farm. Anarchaserver is an open project, even though moderated, and we are using the THF mailing lists and an IRC channel to coordinate the several tasks that need to be achieved.&lt;br /&gt;
&lt;br /&gt;
==== Get involved ==== &lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
Join the [https://lists.riseup.net/www/info/thfeminist] mailing list which is used also for the organisation of the next THF. Present yourself to the admins and then to the list. The list is in spanglish, which means that all messages should be sent including a translation to spanish or english. &lt;br /&gt;
&lt;br /&gt;
Meet us on [http://webchat.freenode.net] the IRC chat on the channel #anarchaserver. We still have to figure out the regularity of our meetings but are leaning towards IRC chat sessions once a month and a distribution of tasks managed through the mailing list.&lt;br /&gt;
&lt;br /&gt;
Have a look at foreseen milestones below and decide what you would like to learn, contribute to.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
==== Future is now: Milestones ====&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
* Documentation &lt;br /&gt;
&lt;br /&gt;
What has happened in anarchaserver Aug14/Jan15? &lt;br /&gt;
&lt;br /&gt;
(Stuff installed, who is admin) basically things that happened at 2013 Constant &amp;quot;Are you being Served&amp;quot; conference, during the THF2014, ESC in Graz had the Ministry of Hacking exhibitionin octiber 2014 and ?  &lt;br /&gt;
&lt;br /&gt;
Prepare Terms of Service and Privacy documentation&lt;br /&gt;
&lt;br /&gt;
Prepare NekroFeministCementry (purpose, howto, zombi sites)&lt;br /&gt;
&lt;br /&gt;
Prepare WP farm (purpose, howto, living sites)&lt;br /&gt;
&lt;br /&gt;
* Accessing&lt;br /&gt;
How to access the [Server]&lt;br /&gt;
&lt;br /&gt;
* Intalling/Testing&lt;br /&gt;
&lt;br /&gt;
Mediagoblin for hosting/sharing files &lt;br /&gt;
&lt;br /&gt;
Tracktracker for follow up of activities in the server and creating tickets for bugs, requests etc&lt;br /&gt;
&lt;br /&gt;
Word press farm testing &lt;br /&gt;
&lt;br /&gt;
* Diffusion &lt;br /&gt;
&lt;br /&gt;
Logo, images, video design about anarchaserver&lt;br /&gt;
&lt;br /&gt;
==== Policy: Aims, working methodologies, sustainability ====&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=39</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=39"/>
		<updated>2014-10-01T23:07:38Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Documentation TransHackFeminist 2014 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
* [[Who was Anarcha?]]&lt;br /&gt;
* [[Anarcha feminesto: Why a feminist server?]]&lt;br /&gt;
* [[Policy: Aims, working methodologies, sustainability]]&lt;br /&gt;
* [[Future is now: Milestones]]&lt;br /&gt;
&lt;br /&gt;
== Documentation TransHackFeminist 2014  ==&lt;br /&gt;
&lt;br /&gt;
[[File:8 THF wangechi-mutu-uterine-catarrh.png|thumb|left|THF-Calafou-2014]]&lt;br /&gt;
&lt;br /&gt;
* [[Servidor feminista/Feminist Server]]&lt;br /&gt;
* [[Anarchagland]]&lt;br /&gt;
* [[Seguridad digital/Digital Security]]&lt;br /&gt;
* [[Taller de teatro de la emancipación / Theatre of the Emancipation Workshop]]&lt;br /&gt;
* [[Taller de Recreación feminista, hackeando vídeos de internet / Feminist Recreation Workshop, hacking videos from the Internet]]&lt;br /&gt;
* [[The Fellatio Modification Project]]&lt;br /&gt;
* [[Satellite Fishing/Pescando satélites]]&lt;br /&gt;
* [[TransHackFeminist/Que significa?/What it means?]]&lt;br /&gt;
* [[R_R/R Radio Ramona and Ruelles]]&lt;br /&gt;
* [[Que es genitalismo?/What Is Genitalism?]]&lt;br /&gt;
* [[Cyborg Romanticism]]&lt;br /&gt;
* [[HerStory]]&lt;br /&gt;
* [[Armas de Destrucción de Misa: diseño en Gimp y HotGlue / Mass Destruction Weapons: Gimp and HotGlue Workshop]]&lt;br /&gt;
* [[Tacticas Feministas en la red/Feminist Tactis in the Net]]&lt;br /&gt;
* [[UpStage, plataforma de codigo abierto para cyberperformaces/Upstage, open source platform for cyberperformance]]&lt;br /&gt;
* [[Cómo jugar en tu ordenador y no cargarte el sistema / How to play in your computer without knocking off the system]]&lt;br /&gt;
* [[Gynepunk BioLab + Del EM, sistema de extracción menstrual / Menstrual extraction systemy]]&lt;br /&gt;
* [[Open Street Map Mapping Party]]&lt;br /&gt;
* [[Bibliotecas publicas digitales/Book Scan]]&lt;br /&gt;
* [[Hacking Gender Construction]]&lt;br /&gt;
* [[Primero Auxilios en Caso aborto y Derrame / First Aid in case of abortion]]&lt;br /&gt;
* [[Experimental Fanzinoteka/ Experimental fanzinotheque]]&lt;br /&gt;
* [[Hacking Acadamia]]&lt;br /&gt;
* [[Los tullidxs están buenos, son transmaricabolleros y follan/ Crips are hot, queer and they fuck]]&lt;br /&gt;
* [[Cafes de la muerte/Death Cafes]] &lt;br /&gt;
* [[Pornotrash]]    &lt;br /&gt;
* [[TransHackfeminist Cabaret]]&lt;br /&gt;
&lt;br /&gt;
* [[Dossier Memoria THF/Memory report THF]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=38</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=38"/>
		<updated>2014-10-01T23:05:55Z</updated>

		<summary type="html">&lt;p&gt;Thf: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
* [[Who was Anarcha?]]&lt;br /&gt;
* [[Anarcha feminesto: Why a feminist server?]]&lt;br /&gt;
* [[Policy: Aims, working methodologies, sustainability]]&lt;br /&gt;
* [[Future is now: Milestones]]&lt;br /&gt;
&lt;br /&gt;
== Documentation TransHackFeminist 2014  ==&lt;br /&gt;
&lt;br /&gt;
[[File:8 THF wangechi-mutu-uterine-catarrh.png|thumb|THF-Calafou-2014]]&lt;br /&gt;
&lt;br /&gt;
* [[Servidor feminista/Feminist Server]]&lt;br /&gt;
* [[Anarchagland]]&lt;br /&gt;
* [[Seguridad digital/Digital Security]]&lt;br /&gt;
* [[Taller de teatro de la emancipación / Theatre of the Emancipation Workshop]]&lt;br /&gt;
* [[Taller de Recreación feminista, hackeando vídeos de internet / Feminist Recreation Workshop, hacking videos from the Internet]]&lt;br /&gt;
* [[The Fellatio Modification Project]]&lt;br /&gt;
* [[Satellite Fishing/Pescando satélites]]&lt;br /&gt;
* [[TransHackFeminist/Que significa?/What it means?]]&lt;br /&gt;
* [[R_R/R Radio Ramona and Ruelles]]&lt;br /&gt;
* [[Que es genitalismo?/What Is Genitalism?]]&lt;br /&gt;
* [[Cyborg Romanticism]]&lt;br /&gt;
* [[HerStory]]&lt;br /&gt;
* [[Armas de Destrucción de Misa: diseño en Gimp y HotGlue / Mass Destruction Weapons: Gimp and HotGlue Workshop]]&lt;br /&gt;
* [[Tacticas Feministas en la red/Feminist Tactis in the Net]]&lt;br /&gt;
* [[UpStage, plataforma de codigo abierto para cyberperformaces/Upstage, open source platform for cyberperformance]]&lt;br /&gt;
* [[Cómo jugar en tu ordenador y no cargarte el sistema / How to play in your computer without knocking off the system]]&lt;br /&gt;
* [[Gynepunk BioLab + Del EM, sistema de extracción menstrual / Menstrual extraction systemy]]&lt;br /&gt;
* [[Open Street Map Mapping Party]]&lt;br /&gt;
* [[Bibliotecas publicas digitales/Book Scan]]&lt;br /&gt;
* [[Hacking Gender Construction]]&lt;br /&gt;
* [[Primero Auxilios en Caso aborto y Derrame / First Aid in case of abortion]]&lt;br /&gt;
* [[Experimental Fanzinoteka/ Experimental fanzinotheque]]&lt;br /&gt;
* [[Hacking Acadamia]]&lt;br /&gt;
* [[Los tullidxs están buenos, son transmaricabolleros y follan/ Crips are hot, queer and they fuck]]&lt;br /&gt;
* [[Cafes de la muerte/Death Cafes]] &lt;br /&gt;
* [[Pornotrash]]    &lt;br /&gt;
* [[TransHackfeminist Cabaret]]&lt;br /&gt;
&lt;br /&gt;
* [[Dossier Memoria THF/Memory report THF]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Dossier_Memoria_THF/Memory_report_THF&amp;diff=37</id>
		<title>Dossier Memoria THF/Memory report THF</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Dossier_Memoria_THF/Memory_report_THF&amp;diff=37"/>
		<updated>2014-09-26T18:40:34Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;'''Proposal Summary Documentation'''  recommendations best to be read after viewing those videos.  Introduction - spider The meaning of THF - spider Convergence Agreement  Res...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Proposal Summary Documentation'''&lt;br /&gt;
&lt;br /&gt;
recommendations best to be read after viewing those videos.&lt;br /&gt;
&lt;br /&gt;
Introduction - spider&lt;br /&gt;
The meaning of THF - spider&lt;br /&gt;
Convergence Agreement&lt;br /&gt;
&lt;br /&gt;
Resume of 2 beta lines of exploration proposed for THF 2014:&lt;br /&gt;
Feminist Server - spider&lt;br /&gt;
Gynepunk - klau&lt;br /&gt;
&lt;br /&gt;
'''Embodied theories'''&lt;br /&gt;
&lt;br /&gt;
Hacking Gender Construction - sophie&lt;br /&gt;
What is genitalism? - sophie&lt;br /&gt;
AnarchaGland - klau&lt;br /&gt;
Hacking the academia – spider&lt;br /&gt;
Crips are hot and they fuck – spider &lt;br /&gt;
Cyborg Romanticism - spider&lt;br /&gt;
&lt;br /&gt;
'''Performative Tactics'''&lt;br /&gt;
&lt;br /&gt;
The Fellatio Modification project - sophie&lt;br /&gt;
Satellite Fishing / Pescando satélites - reni&lt;br /&gt;
Feminist tactics on the net / HerStory - spider&lt;br /&gt;
Zine repositories - klau&lt;br /&gt;
Public digital libraries - spider&lt;br /&gt;
Emancipatory theatre - itzel&lt;br /&gt;
Death Cafes - aileen&lt;br /&gt;
FollonNoiseX - julito&lt;br /&gt;
Cabaret (list somewhere artists and people that did those shows!!!!) - julito / Text pornotrash&lt;br /&gt;
&lt;br /&gt;
'''Liberating technologies'''&lt;br /&gt;
&lt;br /&gt;
Gynepunk BioLab + Del EM, sistema de extracción menstrual / Menstrual extraction system / gynepunk - klau&lt;br /&gt;
Primero Auxilios en Caso aborto y Derrame / First Aid in case of abortion - rox&lt;br /&gt;
Feminist recreation on the net / video - spider&lt;br /&gt;
R_R/R &amp;gt; Radio Ramona and Ruelles / radio - spider&lt;br /&gt;
Armas de destruccion de misa /design - ??&lt;br /&gt;
UpStage / Cyberperformance - sophie&lt;br /&gt;
Cómo jugar en tu ordenador y no cargarte el sistema / How to play in your computer without knocking off the system / Virtual Machines - mayelin&lt;br /&gt;
Digital security / circumvention - spider&lt;br /&gt;
Open Street Map Mapping Party / mapping GPS VS PGS - sophie&lt;br /&gt;
COATI /Spansglish translation&lt;br /&gt;
Screenings / RUINS + Mi sexualidad es una creacion artistica + Dreceres - spider&lt;br /&gt;
&lt;br /&gt;
'''Conclusions + Next THF'''&lt;br /&gt;
&lt;br /&gt;
Next THF&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=TransHackfeminist_Cabaret&amp;diff=36</id>
		<title>TransHackfeminist Cabaret</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=TransHackfeminist_Cabaret&amp;diff=36"/>
		<updated>2014-09-26T18:38:12Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;On the last day of the convergence a Cabaret was organized for celebrating the end of our collective convergence. The cabaret was very meaningful for the philosophy behind the...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;On the last day of the convergence a Cabaret was organized for celebrating the end of our collective convergence. The cabaret was very meaningful for the philosophy behind the THF. It was meaning for the following reasons. &lt;br /&gt;
&lt;br /&gt;
Genderqueer were performing political songs;&lt;br /&gt;
The Pornotrash performance embodied what post-porn is about: liberating the bodies from binaries and from accepted ideas of how certain bodies should look like. It helped to convey the importance of breaking the binaries: binaries between theory and practice, who is producing knowledge and who is consume it, between who can be naked and who can't, between men-bodied people being allowed to show their breast in public, but not women bodied, etc.&lt;br /&gt;
It was also a clear statement that TFH is supporting post-porn subjects making its political stance very clear vis-à-vis certain feminist discourses.   &lt;br /&gt;
All the technical set up and management were prepared by the participants (setting up the sound system, the stage, etc.) reflecting a strong DYI ethos in addition demonstrating that feminist, women, genderqueer and trans can do it! &lt;br /&gt;
This idea that life and hacking (gender hacking/bending) is about performances.&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=35</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=35"/>
		<updated>2014-09-26T18:37:55Z</updated>

		<summary type="html">&lt;p&gt;Thf: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[File:8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
* [[Who was Anarcha?]]&lt;br /&gt;
* [[Anarcha feminesto: Why a feminist server?]]&lt;br /&gt;
* [[Policy: Aims, working methodologies, sustainability]]&lt;br /&gt;
* [[Future is now: Milestones]]&lt;br /&gt;
&lt;br /&gt;
== Documentation TransHackFeminist 2014  ==&lt;br /&gt;
&lt;br /&gt;
* [[Servidor feminista/Feminist Server]]&lt;br /&gt;
* [[Anarchagland]]&lt;br /&gt;
* [[Seguridad digital/Digital Security]]&lt;br /&gt;
* [[Taller de teatro de la emancipación / Theatre of the Emancipation Workshop]]&lt;br /&gt;
* [[Taller de Recreación feminista, hackeando vídeos de internet / Feminist Recreation Workshop, hacking videos from the Internet]]&lt;br /&gt;
* [[The Fellatio Modification Project]]&lt;br /&gt;
* [[Satellite Fishing/Pescando satélites]]&lt;br /&gt;
* [[TransHackFeminist/Que significa?/What it means?]]&lt;br /&gt;
* [[R_R/R Radio Ramona and Ruelles]]&lt;br /&gt;
* [[Que es genitalismo?/What Is Genitalism?]]&lt;br /&gt;
* [[Cyborg Romanticism]]&lt;br /&gt;
* [[HerStory]]&lt;br /&gt;
* [[Armas de Destrucción de Misa: diseño en Gimp y HotGlue / Mass Destruction Weapons: Gimp and HotGlue Workshop]]&lt;br /&gt;
* [[Tacticas Feministas en la red/Feminist Tactis in the Net]]&lt;br /&gt;
* [[UpStage, plataforma de codigo abierto para cyberperformaces/Upstage, open source platform for cyberperformance]]&lt;br /&gt;
* [[Cómo jugar en tu ordenador y no cargarte el sistema / How to play in your computer without knocking off the system]]&lt;br /&gt;
* [[Gynepunk BioLab + Del EM, sistema de extracción menstrual / Menstrual extraction systemy]]&lt;br /&gt;
* [[Open Street Map Mapping Party]]&lt;br /&gt;
* [[Bibliotecas publicas digitales/Book Scan]]&lt;br /&gt;
* [[Hacking Gender Construction]]&lt;br /&gt;
* [[Primero Auxilios en Caso aborto y Derrame / First Aid in case of abortion]]&lt;br /&gt;
* [[Experimental Fanzinoteka/ Experimental fanzinotheque]]&lt;br /&gt;
* [[Hacking Acadamia]]&lt;br /&gt;
* [[Los tullidxs están buenos, son transmaricabolleros y follan/ Crips are hot, queer and they fuck]]&lt;br /&gt;
* [[Cafes de la muerte/Death Cafes]] &lt;br /&gt;
* [[Pornotrash]]    &lt;br /&gt;
* [[TransHackfeminist Cabaret]]&lt;br /&gt;
&lt;br /&gt;
* [[Dossier Memoria THF/Memory report THF]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=The_Fellatio_Modification_Project&amp;diff=34</id>
		<title>The Fellatio Modification Project</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=The_Fellatio_Modification_Project&amp;diff=34"/>
		<updated>2014-09-26T18:36:41Z</updated>

		<summary type="html">&lt;p&gt;Thf: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Abstract: The  Fellatio Modification Project is a series of oral modifications with dental technology and tissue  engineering. The purpose of this project is to enhance the physical  pleasure of having oral sex in gay people. &lt;br /&gt;
Metodology: There are 3 stages in this project.&lt;br /&gt;
For more infor visit: bioArt Taiwan&lt;br /&gt;
Stage 1: Modify  the orthodontic retainer that would be worn by patients by  covering  the upper palate of the retainer with soft denture reline material,  which emulates real soft tissue, to create an embossed surface. During oral sex, the back and forth contacts with the raised surface would enhance the physical pleasure. &lt;br /&gt;
Stage 2 : Enable  for the raised surface from the orthodontic retainer to have a  closer  resemblance to the actual oral tissues, I replace the soft  denture  reline material with tissues constructed from tissue-engineering   technology.&lt;br /&gt;
Stage 3: I no longer use orthodontic retainer as a tool to enhance the pleasure  from oral sex. Instead, I will surgically implant real embossed soft  tissue constructed by engineering technology on the upper palate of the   patient, thus creating a permanent modification to the oral cavity   structure. &lt;br /&gt;
 Most  medical technologies are used for curing diseases, healing  injured  bodies, and restoring to patients to perform normal functions,  but this  project is using the technology to extend the oral function.  There are  three main functions of oral cavity: aesthetics,  pronunciation, and  chewing. However this project will focus on another  function: “Sex”,  which is never mentioned on textbooks. There is no  denying that human  beings always have the desire to pursue the physical  pleasure of sex.  Therefore, this project wants to discuss the relations  among sex,  technology, human and the society. It attempts to push the  limits and  possibilities of body modification.&lt;br /&gt;
This  project is a cooperation between Fred Kuang-Yi Ku from bioArt Taiwan with Dr. Yuan-Min Lin’s Tissue Engineering  and  Regenerative Medicine Laboratory in the Department of Dentistry, National Yang-Ming University.&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Hacking_Acadamia&amp;diff=33</id>
		<title>Hacking Acadamia</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Hacking_Acadamia&amp;diff=33"/>
		<updated>2014-09-26T18:35:58Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;The starting point with this session was a felt uneasiness with the division between practice and theory. How do you position yourself as a feminist or a transfeminist in the ...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The starting point with this session was a felt uneasiness with the division between practice and theory. How do you position yourself as a feminist or a transfeminist in the academia? This session is rooted in personal experiences of how to hack academia in concrete terms to be able/or try to attempt to position oneself as a trans/feminist within a university setting. To be able to survive in academia you need to hack it.  Those who have been able to hack it at a personal or collective level have a responsibility to share the ways in which this was done so other can learn and remix it. Sharing tactics that can be applies all is thus important. This gives us strength and courage to continue our work in what is often a very isolating experience. &lt;br /&gt;
The relationship between academia and knowledge production is very problematic. Sometimes we, as academics, have a form of shame because it is not easy to position ourselves between practice and theory – between activist and academic lives.  In some country, the division between theory and practice is more pronounced. This is often linked to the idea of universalism. The idea that every citizens are the same. This is very problematic. In the country of Foucault, Derrida and the post-structuralists, that is France, the distance between your personal life and your research is separate. The problem arises when you are an activist researcher. What not to do to foster the gap between theoretical production and practice? How can we produce “restitution research” on people who continuously put themselves on the line? How and what to do to create an environment that will slowly 'feels like home' and where you develop a feeling of belonging (Alvarez 2013: 50)? How can we avoid the interiorizing of academic norms that, through the creation of boundaries create mental containment, control and limit our practice? &lt;br /&gt;
Rachele Borghi aka Zarra Bonheur example (extract from performing academy).&lt;br /&gt;
“I'm a queerlesbianfeminist pornoactivademic geographer. My research activities have always featured the reflection on the academic practices and on my positioning in relation to research and fieldwork. The contact with queer groups and collectives made the issue more and more significant and raised the urgency to find and experiment effective approaches that could help me to avoid replicating the duo theory/practice. Zarra Bonheur is born to search for answers to these persistent questions, to find a ‘teotetic’ way out to conceptual cages, to experiment the embodied research, to convey subjects, objectives and concepts through my body.”&lt;br /&gt;
Watch her performing academy hack: &lt;br /&gt;
http://www.dailymotion.com/video/xy53hh_queer-days-rachele-borghi_shortfilms &lt;br /&gt;
Recommended reading are: &lt;br /&gt;
Beyond scholar activism: Making strategic interventions inside and outside the neoliberal university &lt;br /&gt;
Constructing a Relational Space between ‘Theory’ and ‘Activism’,or (Re)thinking Borders&lt;br /&gt;
The cultural role of universities in the community: revisiting the university - community debate&lt;br /&gt;
Demand the Possible: Journeys in Changing ourWorld as a Public Activist-Scholar&lt;br /&gt;
The Border between Theory and Activism&lt;br /&gt;
Militant Research Hand-Book&lt;br /&gt;
Porn's pedagogies: teaching porn studies in the academic–corporate complex&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Hacking_Gender_Construction&amp;diff=32</id>
		<title>Hacking Gender Construction</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Hacking_Gender_Construction&amp;diff=32"/>
		<updated>2014-09-26T18:34:53Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;Abstract: Before hacking gender, it might be useful to have a look at how gender is constructed in society: Why do people usually ‘see’ only two genders? Which ‘tools’...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Abstract: Before hacking gender, it might be useful to have a look at how gender is constructed in society: Why do people usually ‘see’ only two genders? Which ‘tools’ are used to establish a bias between the concepts of ‘male’ and ‘female’? … And what can ‘hacking’ mean in this context? This will be a very basic introduction into the (de)construction of gender and some thoughts about ‘hacking’ in a broader sense.&lt;br /&gt;
Metodology:  I’d like to give a rather short talk  I also try to transform abstract theory into handy comic-style images) and afterwards collect ideas on how and where you want to hack gender or which useful techniques you already tried.&lt;br /&gt;
Recomended lectures: you like and if you understand German, you can find the script on my blog (under the section ‘Material’): heterosexismushacken.blogsport.de&lt;br /&gt;
Step #1: install totalitarianism: Something applied on you and you can't escape. [hand-drawn diagram - see slides]&lt;br /&gt;
Step #2: Create binaries: Male / Female. This classification is constructed, made up of norms and values. Often people say biological sexes are fixed, but it's untrue because there's no unambiguous assignment (e.g., chromosomes, gonades (testicles, ovaries), body shapes, brains etc. Everyone's body is different&lt;br /&gt;
Step#3: apply binary categories: Attribute for distinction, assignment according to attribute, gender roles (e.g., how they dress, how they move ...)&lt;br /&gt;
Step #4: learning to 'see' only two categories: three basic (axiomatic) assumptions: &lt;br /&gt;
either/or&lt;br /&gt;
it's natural: gender is based on sex&lt;br /&gt;
it's constant: someone you met today is a woman, who will stay as a woman 50 years from now on.&lt;br /&gt;
In German for instance, there's only one word for gender and sex. It is thus difficult to explain the gender aspects.      &lt;br /&gt;
Step #5: learning to 'be read' 'be seen' as member of one category:&lt;br /&gt;
    &amp;quot;doing gender&amp;quot; in daily life&lt;br /&gt;
    &amp;quot;performing gender roles&amp;quot;&lt;br /&gt;
    &amp;quot;making gender assignment visible&amp;quot;&lt;br /&gt;
    &amp;quot;enact gender attributes&amp;quot;    &lt;br /&gt;
Step #6: rating people related to gender assignment: &lt;br /&gt;
Judging people (others and yourself) assuming they are female / male, if they are doing gender correctly. &lt;br /&gt;
This takes place in a social environment (people around you decide what gender you are)&lt;br /&gt;
being rated in regard of gender roles&lt;br /&gt;
Step #7: teaching people the 'right' behaviour related to gender assignment:&lt;br /&gt;
socialisation happens schools, media, hospitals ... &lt;br /&gt;
This shapes behaviour through interactions (naming, addressing, demonstrating, rules, daily routines ... ) and institutions&lt;br /&gt;
Pictures, languages, stories also influences,  e.g., toilet signs, &amp;quot;is it a boy or a girl?&amp;quot; (recommended response: &amp;quot;my baby is very healthy. thanks for asking&amp;quot;)&lt;br /&gt;
How to cope? we can try to change language. language is a living system. how to teach your kids?&lt;br /&gt;
We are all part of 'them'; we are all responsible. Sub-consciously we all do it from time to time.        &lt;br /&gt;
Step #8: make binaries asymmetric (rather unequal): &lt;br /&gt;
gender construction is inherently sexist. People not only put gender assignment on others, but also hierarchy.  e.g., men are rational and women are not? (negation), men are better with technology and women less (graduation), men are more rational and women are emotional (complementation / contrasts)&lt;br /&gt;
Step #9: represent binaries asymmetric (systematically): &lt;br /&gt;
In Western linguistic systems, male words are used to refer to everybody e.g., men = human beings, e.g.: Children books with humanised animals images with sexes; in movies, ask: are there more than 1 female character? are they talking to each other? are they talking about topics other than men? &lt;br /&gt;
Step #10: represent binaries asymmetric (quantitative):&lt;br /&gt;
Androcentric view: mostly about men, in the view of men,  the word 'God' (Dio) has the male pronoun, &amp;quot;the male gays&amp;quot;     &lt;br /&gt;
Definition of Hacking:&lt;br /&gt;
What does 'hacking' mean in this context:&lt;br /&gt;
Original definitions of 'hack' or 'hacking':&lt;br /&gt;
        - Tech model railroad Club (MIT): hacker is someone who applies ingenuity to create a celver result, called a 'hack'.&lt;br /&gt;
        - In a german context like the Computer Chaos Club (CCC): disrespectful and creative usage of technology in daily life (Lehnhardt 1988) which can imply social engineering.&lt;br /&gt;
To the presenter of this workshop: hacking is self-determined, do things differently, examination and play with things, intervene (hopefully successful) with given objects and structures.&lt;br /&gt;
To summarise: 1) hacking means finding extraordinary ways to solve problems - even and especially for problems the majority is not aware of - because they are part of the unquestioned, part of the system. 2) Hacking also means taking joy in playing with the allowed and the forbidden, in crossing boundaries of norms and conventions, in autonomous exploring, in questioning, reinterpreting and reclaiming what is given. &lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Bibliotecas_publicas_digitales/Book_Scan&amp;diff=31</id>
		<title>Bibliotecas publicas digitales/Book Scan</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Bibliotecas_publicas_digitales/Book_Scan&amp;diff=31"/>
		<updated>2014-09-26T18:33:19Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot; 0) Introducción  - Bibliotecas publicas digitales  Dentro del catalogo de los grandes avances históricos, las bibliotecas públicas forman parte de uno de los fenómenos de...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
0) Introducción  - Bibliotecas publicas digitales&lt;br /&gt;
&lt;br /&gt;
Dentro del catalogo de los grandes avances históricos, las bibliotecas&lt;br /&gt;
públicas forman parte de uno de los fenómenos de los cuales nos sentimos&lt;br /&gt;
mas orgullosas, seguramente junto a la educación y la salud publica, la&lt;br /&gt;
declaración universal de los derechos humanos, el método científico, la&lt;br /&gt;
wikipedia o  el software libre.&lt;br /&gt;
&lt;br /&gt;
Se trata de una de esas infraestructuras casi invisibles que solo vamos&lt;br /&gt;
notando cuando empiezan a desaparecer. Durante mucho tiempo, las&lt;br /&gt;
bibliotecas publicas se han constituido como el lugar desde el cual&lt;br /&gt;
poder acceder al conocimiento aunque solían ser demasiado dependiente de&lt;br /&gt;
los presupuestos siempre inestables de los estados del “bienestar” o de&lt;br /&gt;
los recursos limitados de algunos ricos mecenas.&lt;br /&gt;
&lt;br /&gt;
Internet ha volcado nuestras interpretaciones de lo que tomábamos como&lt;br /&gt;
dado y posible. El sueño de poder acceder todas a todo el conocimiento&lt;br /&gt;
se volvió a nuestro alcance. Parecía sólo una cuestión de difusión.&lt;br /&gt;
Saber vislumbrar cuando las curvas de distribución de los ordenadores&lt;br /&gt;
personales y el acceso a Internet acabarían por unirse para hacer que&lt;br /&gt;
ese acceso universal al conocimiento se volviese realidad. Sin embargo,&lt;br /&gt;
el desarrollo de las bibliotecas publicas en la era de Internet parece&lt;br /&gt;
ir directamente en la dirección opuesta, haciendo que puedan fácilmente&lt;br /&gt;
desaparecer.&lt;br /&gt;
&lt;br /&gt;
Muchas bibliotecas publicas no pueden recibir, y a menudo tampoco&lt;br /&gt;
comprar, los libros editados por grandes editoriales1. Los libros que ya&lt;br /&gt;
conforman su catalogo deben ser a veces destruidos después de prestarlos&lt;br /&gt;
26 (?!?) veces. Se esta perdiendo la batalla del mercado dominado por&lt;br /&gt;
nuevos actores como Amazon, Google y Apple.&lt;br /&gt;
&lt;br /&gt;
Pero las revoluciones emancipadoras también forman parte de los&lt;br /&gt;
fenómenos de los cuales podemos mostrarnos mas orgullosas. Empoderar las&lt;br /&gt;
personas para que cuenten con los medios necesarios para alcanzar sus&lt;br /&gt;
sueños. No podemos renunciar a las bibliotecas publicas en la edad de&lt;br /&gt;
Internet, ni al sueño de un acceso universal a todo el conocimiento&lt;br /&gt;
humano. Por ello activistas, documentalistas, ciudadanas, artistas,&lt;br /&gt;
hackers, y muchas otras, están creando las circunstancias para volver&lt;br /&gt;
sus sueños realidad y de paso contar como dijo Melvil Dewey con&lt;br /&gt;
“escuelas libres y bibliotecas libres para cada alma”.3&lt;br /&gt;
La propuesta es  la siguiente:  Hagamos unos catalogo de todos los&lt;br /&gt;
libros que ya hemos descargado y compartámoslo! Al fin y al cabo una&lt;br /&gt;
biblioteca publica consiste en:&lt;br /&gt;
&amp;gt; Un acceso libre para cada miembro de la sociedad a libros&lt;br /&gt;
&amp;gt; Unos catálogos de los libros y documentos disponibles&lt;br /&gt;
&amp;gt; Unas personas bibliotecarias&lt;br /&gt;
&lt;br /&gt;
Con libros preparados para ser compartidos, meticulosamente&lt;br /&gt;
categorizados, cada persona puede volverse una bibliotecaria. Cuando&lt;br /&gt;
todas somos bibliotecarias, las bibliotecas publicas se encuentran en&lt;br /&gt;
todos los lugares. Así de sencillo.&lt;br /&gt;
&lt;br /&gt;
Muy poco habría sido posible si Sean Dockray no hubiese empezado&lt;br /&gt;
Aaaaarg.org, Dušan Barok Monoskop, Sebastian Luetgert y Jan Gerber&lt;br /&gt;
Pirate Cinema &amp;amp; pad.ma, Kenneth Goldsmith UbuWeb, Henry Warwick&lt;br /&gt;
Alexandria project, Piratbyrån The Pirate Bay y  si los hackers detrás&lt;br /&gt;
de Library Genesis no nos hubiesen dado la oportunidad de descargar su&lt;br /&gt;
catalogo de casi millón de libros. En los siguientes enlaces pueden&lt;br /&gt;
encontrar varios ejemplos de bibliotecas publicas digitales.&lt;br /&gt;
&lt;br /&gt;
+ info:&lt;br /&gt;
http://monoskop.org/Monoskop&lt;br /&gt;
http://ubu.com/&lt;br /&gt;
http://aaaaarg.org/(repositorio de libros)&lt;br /&gt;
http://thepublicschool.org/&lt;br /&gt;
http://libgen.org/libreria genesis&lt;br /&gt;
http://cataleg.xarxabibliosocials.org/portal/&lt;br /&gt;
http://625lineas.com/epl/&lt;br /&gt;
http://theanarchistlibrary.org/&lt;br /&gt;
http://knol.pw/  (Para comprar el libro que buscas a precios super&lt;br /&gt;
reducidos)&lt;br /&gt;
http://wolnelektury.pl/&lt;br /&gt;
http://www.reddit.com/r/scholar  (Una nube para documentos academicos)&lt;br /&gt;
http://www.mi2.hr&lt;br /&gt;
Imperial Library of Trantor. Repositorio de libros disponible solo en la&lt;br /&gt;
red Tor.&lt;br /&gt;
https://xfmro77i3lixucja.onion.to/(Se puede acceder desde la clearnet&lt;br /&gt;
mediante esta pasarela)&lt;br /&gt;
http://pad.ma&lt;br /&gt;
http://ge.tt&lt;br /&gt;
http://ge.tt/2YaYETU&lt;br /&gt;
&lt;br /&gt;
1) Fabricar y aprender a usar (y cuidar)  un escáner de libros.&lt;br /&gt;
&lt;br /&gt;
La primera fase del encuentro consistio en montar el escaner de libros&lt;br /&gt;
[1] diseñado y construido por Voja Antonic en el marco del proyecto&lt;br /&gt;
Memoryoftheworld.org. Partiendo de un manual [2] desarrollado en inglés&lt;br /&gt;
el pasado més de octubre durante un hackaton organizado en Utrecht [3]&lt;br /&gt;
unas participantes del encuentro se dedicaron a su traducción en&lt;br /&gt;
castellano [4]. El manual también se encuentra en formato latex para&lt;br /&gt;
imprimir [5].&lt;br /&gt;
&lt;br /&gt;
Comentarios sobre el escaneo y procesamiento (Roman):&lt;br /&gt;
&lt;br /&gt;
- después de renumerar los ficheros en &amp;quot;left camera&amp;quot; y &amp;quot;right camera&amp;quot;,&lt;br /&gt;
conviene COPIARLOS a &amp;quot;all&amp;quot; en vez de moverlos; haciendo esto nos queda&lt;br /&gt;
una copia de resguardo en ambas carpetas, por si algo va mal en &amp;quot;all&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- cuando ponemos los ficheros renumerados en la carpeta &amp;quot;all&amp;quot; conviene&lt;br /&gt;
chequear que el número de ficheros corresponde al número del último&lt;br /&gt;
fichero en la carpeta, por ejemplo si el último fichero en la carpeta es&lt;br /&gt;
&amp;quot;387.jpg&amp;quot; el número de ficheros debe ser 387.&lt;br /&gt;
&lt;br /&gt;
Finalmente, el legendario inventor Voja Antonić nos dio una charla sobre&lt;br /&gt;
la prehistoria de la cultura hacker en los últimos años 70 y primero 80&lt;br /&gt;
en la antigua Yugoslavia. Antonić nos habló de cómo se podía ser hacker&lt;br /&gt;
en un contexto en el que todavía ni siguiera existían los ordenadores&lt;br /&gt;
personales, y cómo se difundía y comunicaba la innovación antes del&lt;br /&gt;
acceso masivo a internet. Nos habló de cómo diseñó el primer ordenador&lt;br /&gt;
personal DIY en Yugoslavia, el mítico Galaksija, y del sentido ético del&lt;br /&gt;
trabajo de un ingeniero que fue pionero en muchas cosas en su entorno,&lt;br /&gt;
pero que donó todo su trabajo al dominio público.&lt;br /&gt;
Puedes escuchar la charla que dio en este enlace [6] (Recorded by&lt;br /&gt;
Acoustic Mirror).&lt;br /&gt;
&lt;br /&gt;
+ info:&lt;br /&gt;
[1]&lt;br /&gt;
http://www.memoryoftheworld.org/es/blog/2012/10/28/our-beloved-bookscanner/&lt;br /&gt;
[2] http://ge.tt/6GcAE4c1&lt;br /&gt;
[3]&lt;br /&gt;
http://www.monnik.org/workshops/free-libraries-for-every-soul-hackathon/&lt;br /&gt;
[4] http://titanpad.com/Manual-de-escaneado-de-libros&lt;br /&gt;
[5] https://www.writelatex.com/976064myydnm#/2253265/&lt;br /&gt;
[6]&lt;br /&gt;
https://archive.org/details/20140418VojaAntonicTalkHackTheBiblioCalafou&lt;br /&gt;
http://www.diybookscanner.org(Una pagina mantenida por un aficionado a&lt;br /&gt;
los escaneres de libros)&lt;br /&gt;
http://www.tabakalera.eu/es/proiektuak/scanner-ibiltaria-3/(Scanner&lt;br /&gt;
libre construido con impresora 3D en Tabakalera (Donosti) y proyecto de&lt;br /&gt;
scanner itinerante)&lt;br /&gt;
http://hackerspace.be/ScanBot(Hacker Space Bruxelles scanner)&lt;br /&gt;
&lt;br /&gt;
Pase de Cine: &amp;quot;Farenheit 451&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2) Programas y aplicaciones libres para construir catálogos&lt;br /&gt;
&lt;br /&gt;
Ningún libro debería dejar nunca la red de catálogos. Si se transfiere&lt;br /&gt;
debería ir de un catalogo situado en un punto hacia otro catalogo&lt;br /&gt;
situado en otro punto [0]. La primera pieza de nuestro mosaico&lt;br /&gt;
rompecabezas es la herramienta de software que permitirá a cada usuario&lt;br /&gt;
final crear y mantener su catalogo de libros. Hemos encontrado, así como&lt;br /&gt;
otros 10 millones de usuarios, esa herramienta. Se trata de Calibre [1].&lt;br /&gt;
Con ella es fácil volverse un bibliotecario.&lt;br /&gt;
&lt;br /&gt;
La siguiente etapa es conectar los bibliotecarios Calibre entre si. En&lt;br /&gt;
general, estos usan sus catálogos Calibre dentro de sus ordenadores&lt;br /&gt;
personales dentro de redes de área locales. Hemos desarrollado&lt;br /&gt;
herramientas para que pueden conectarse entre ellos sin problemas.&lt;br /&gt;
Cuando lo hacen pueden sincronizar sus catálogos, recomendar y compartir&lt;br /&gt;
libros [2] plugin let's share books. Los bibliotecarios se vuelven&lt;br /&gt;
cyber-bibliotecarios.&lt;br /&gt;
&lt;br /&gt;
Las herramientas contemplan desde enlaces magnéticos para importar&lt;br /&gt;
libros directamente desde el blog en el cual son recomendados hacia&lt;br /&gt;
Calibre; ayudas para buscar y descargar grandes repositorios de libros&lt;br /&gt;
directamente desde Calibre (e.g. Library Genesis, Ebookee,&lt;br /&gt;
Aaaaarg.org…); una herramienta para contextualisar libros con contenidos&lt;br /&gt;
de la Wikipedia así como también se encuentra un navegador experimental&lt;br /&gt;
para navegar dentro de grandes catálogos.&lt;br /&gt;
&lt;br /&gt;
El desarrollo de software cubre un amplio espectro de tecnologías:&lt;br /&gt;
hackear la wikipedia, extensiones para el navegador web, librerías&lt;br /&gt;
JavaScript, herramientas de red, enrutadores, NAS (networked attached&lt;br /&gt;
storage) así como también dispositivos embebidos. El grupo de trabajo&lt;br /&gt;
Bookmagnet esta trabajando en un conjunto de herramientas, estándares y&lt;br /&gt;
convenciones acerca de como compartir libros en las futuras bibliotecas&lt;br /&gt;
publicas p2p.&lt;br /&gt;
&lt;br /&gt;
Sobre artículos académicos:&lt;br /&gt;
- Código DOI que identifica cada artículo. Encuentras el artículo con su&lt;br /&gt;
código pero debes pagar (JStore, por ejemplo). Entonces copias el código&lt;br /&gt;
DOI y lo buscas en LibGen o en Scholar (http://www.reddit.com/r/scholar)&lt;br /&gt;
&amp;lt;http://www.reddit.com/r/scholar%29&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Sobre Catalogación:&lt;br /&gt;
- CDU: Clasificación Decimal Universal. 0-9 grandes temas. La mayoría de&lt;br /&gt;
bibliotecas catalogan así; Copia i Difon ha tomado esta base.&lt;br /&gt;
- PMB: programa que conecta con los metadatos vía z93. Conecta con&lt;br /&gt;
grandes bibliotecas.&lt;br /&gt;
&lt;br /&gt;
Conceptos:&lt;br /&gt;
- Libros huérfanos: http://en.wikipedia.org/wiki/Orphan_works&lt;br /&gt;
- &amp;quot;Patrimonio Editorial&amp;quot;&lt;br /&gt;
&lt;br /&gt;
+ info:&lt;br /&gt;
[0]&lt;br /&gt;
http://www.memoryoftheworld.org/es/blog/2012/11/26/catalogo-de-punto-a-punto/&lt;br /&gt;
[1] http://calibre-ebook.com/y&lt;br /&gt;
http://www.cobdc.net/programarilliure/crea-servidor-ebooks-calibre/&lt;br /&gt;
[2] https://github.com/marcellmars/letssharebooks+&lt;br /&gt;
http://manual.calibre-ebook.com/gui.html#connect-share. Todos los libros&lt;br /&gt;
compartiéndose en tiempo real mediante el plugin letssharebooks de&lt;br /&gt;
calibre: https://library.memoryoftheworld.org/+&lt;br /&gt;
https://chat.memoryoftheworld.org/&lt;br /&gt;
http://helibtech.com/Open%20SourceHELibTech wiki (open source library&lt;br /&gt;
software page)&lt;br /&gt;
http://www.esi.ac.uk/meetings/1114/videos/4807(Modelo de negocio par un&lt;br /&gt;
sistema de manntenimiento de bibliotecas de código abierto)&lt;br /&gt;
http://www.lsoft.com/SCRIPTS/WL.EXE?SL1=LIS-OSS&amp;amp;H=JISCMAIL.AC.UK(Lista&lt;br /&gt;
de correo acerca de sistemas y programas de código abierto para&lt;br /&gt;
bibliotecas)&lt;br /&gt;
http://ki.ber.kom.uni.st&amp;gt;&amp;gt; redirected to:&lt;br /&gt;
http://protopage.com/kiberkomunist(pagina web de Marcell Mars,&lt;br /&gt;
desarollador del proyecto memoryoftheworld.org)&lt;br /&gt;
&lt;br /&gt;
GPrename y Scan tailor&lt;br /&gt;
&lt;br /&gt;
El proceso de digitalización de la Biblioteca Pública se divide así en&lt;br /&gt;
los siguientes pasos:&lt;br /&gt;
1. Creación digital de imágenes de páginas de un libro,&lt;br /&gt;
2. Transferencia manual de archivos de imagen al ordenador para&lt;br /&gt;
post-producción,&lt;br /&gt;
3. Renombramiento automático de archivos, ordenando páginas pares e&lt;br /&gt;
impares, rotación de imágenes y subida a un almacenamiento en la nube,&lt;br /&gt;
4. Transformación manual de las imágenes en archivos .tiff en ScanTailor&lt;br /&gt;
5. Reconocimiento óptico de caracteres y creación de archivos PDF en&lt;br /&gt;
gscan2pdf&lt;br /&gt;
&lt;br /&gt;
Una vez que las páginas del libro han sido fotografiadas, tienen que ser&lt;br /&gt;
transferidas al ordenador y preparadas para post-producción.  esta&lt;br /&gt;
documentación se centrará en una que puede ser usada en la mayoría de&lt;br /&gt;
los sistemas operativos: ScanTailor. ScanTailor se puede descargar desde&lt;br /&gt;
http://scantailor.sourceforge.net/. Puedes ver un vídeotutorial más&lt;br /&gt;
detallado de ScanTailor en:  http://vimeo.com/12524529.&lt;br /&gt;
&lt;br /&gt;
+ info:&lt;br /&gt;
http://gprename.sourceforge.net/&lt;br /&gt;
http://scantailor.org/&lt;br /&gt;
&lt;br /&gt;
Reconocimiento óptico de caracteres (OCR) : De las imagenes a las palabras&lt;br /&gt;
&lt;br /&gt;
Antes de que los archivos gráficos terminen en un e-book, queremos&lt;br /&gt;
transformar la imagen del texto en texto real que pueda ser encontrado&lt;br /&gt;
mediante un buscador, subrayado, copiado y transformado. Esta&lt;br /&gt;
funcionalidad la proporciona el Reconocimiento Óptico de Caracteres (ORC&lt;br /&gt;
por sus siglas en inglés). Esta tarea es difícil técnicamente, y depende&lt;br /&gt;
del idioma, el guión, la fuente usada en el texto y la calidad de la&lt;br /&gt;
impresión. Desafortunadamente no hay muchas herramientas de OCR que sean&lt;br /&gt;
buenas en esto. Hay, sin embargo, una solución software libre&lt;br /&gt;
relativamente buena: Tesseract (http://code.google.com/p/tesseract-ocr/)&lt;br /&gt;
&amp;lt;http://code.google.com/p/tesseract-ocr/%29&amp;gt;, que tiene un buen&lt;br /&gt;
rendimiento, un buen manejo de idiomas y que puede ser entrenado incluso&lt;br /&gt;
para obtener mejores resultados, aunque tiene problemas. Soluciones&lt;br /&gt;
comerciales y propietarias (como por ejemplo Abby FineReader) a veces&lt;br /&gt;
proporcionan mejores resultados.&lt;br /&gt;
&lt;br /&gt;
Tesseract es un motor OCR libre. Fue desarrollado originalmente por&lt;br /&gt;
Hewlett Packard como software propietario entre 1985 y 1995. Tras diez&lt;br /&gt;
años sin ningún desarrollo, fue liberado como código abierto en el año&lt;br /&gt;
2005 por Hewlett Packard y la Universidad de Nevada, Las Vegas.&lt;br /&gt;
Tesseract es desarrollado actualmente por Google y distribuido bajo la&lt;br /&gt;
licencia Apache, versión 2.0. Tesseract está considerado como uno de los&lt;br /&gt;
motores OCR libres con mayor precisión disponibles actualmente. En 1995,&lt;br /&gt;
Tesseract era uno de los tres mejores motores OCR en cuanto a precisión,&lt;br /&gt;
además está disponible para Linux, Windows y Mac OS X, sin embargo, sólo&lt;br /&gt;
ha sido probado por los desarrolladores en Windows y Ubuntu. Hasta la&lt;br /&gt;
versión 2, Tesseract sólo podía aceptar como entrada imágenes de una&lt;br /&gt;
sola columna en formato TIFF. En estas primeras versiones no se incluía&lt;br /&gt;
análisis de patrones, y por tanto, las imágenes con múltiples columnas o&lt;br /&gt;
anotaciones producían resultados ilegibles. Desde la versión 3,&lt;br /&gt;
Tesseract soporta el formato en el texto y el análisis del patrón de la&lt;br /&gt;
página. A través de la biblioteca Leptonica, se consigue la&lt;br /&gt;
compatibilidad con nuevos formatos de imagen, además, se puede detectar&lt;br /&gt;
si el texto proporcional o monoespaciado. Tesseract puede procesar&lt;br /&gt;
inglés, francés, italiano, alemán, español, portugués brasileño y&lt;br /&gt;
neerlandés, y puede ser entrenado para funcionar con otros idiomas.&lt;br /&gt;
&lt;br /&gt;
HowTo:&lt;br /&gt;
&lt;br /&gt;
Batch processing of TIF files with Tesseract 3.03 for this. [0]. On&lt;br /&gt;
Debian unstable and testing you can install Tesseract like this:&lt;br /&gt;
&lt;br /&gt;
   # This installs installs tesseract:&lt;br /&gt;
   apt-get install tesseract-ocr tesseract-ocr-spa tesseract-ocr-eng&lt;br /&gt;
   # This converts all the files IN THE CURRENT DIRECTORY to OCRed PDF&lt;br /&gt;
files:&lt;br /&gt;
   time for i in *tif; do b=`basename &amp;quot;$i&amp;quot; .tif`; tesseract -l spa &amp;quot;$i&amp;quot;&lt;br /&gt;
&amp;quot;$b&amp;quot; pdf; done&lt;br /&gt;
   # This merges all the PDF files into a single PDF.&lt;br /&gt;
   pdftk *pdf cat output merged.pdf&lt;br /&gt;
&lt;br /&gt;
(.)Ubuntu Trusty Tahr 14.04 ya tiene la versión de Tesseract 3.0.3 en&lt;br /&gt;
paquetes .deb&lt;br /&gt;
&lt;br /&gt;
*Renaming in KDE*&lt;br /&gt;
&lt;br /&gt;
On the last tab &amp;quot;4. Filename&amp;quot; select &amp;quot;Filename: Custom name&amp;quot; and enter&lt;br /&gt;
&amp;quot;#{1;2}&amp;quot; for left camera, #{2;2}&amp;quot; for right camera (without the double&lt;br /&gt;
quotes...) and enter ## as a Prefix.&lt;br /&gt;
&lt;br /&gt;
Under &amp;quot;Number&amp;quot; make sure that &amp;quot;Start Index&amp;quot; is 0 and &amp;quot;Number of digits&amp;quot;&lt;br /&gt;
is 3 (should be for books under 1000 pages ??)&lt;br /&gt;
&lt;br /&gt;
3) Canales de encuentro&lt;br /&gt;
Te puedes suscribir a esta lista para publicar información de interés&lt;br /&gt;
para el desarrollo de bibliotecas publicas digitales.&lt;br /&gt;
hackthebiblio@lists.riseup.net&lt;br /&gt;
&lt;br /&gt;
Puedes encontrarnos en el chat: https://chat.memoryoftheworld.org/&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Primero_Auxilios_en_Caso_aborto_y_Derrame_/_First_Aid_in_case_of_abortion&amp;diff=30</id>
		<title>Primero Auxilios en Caso aborto y Derrame / First Aid in case of abortion</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Primero_Auxilios_en_Caso_aborto_y_Derrame_/_First_Aid_in_case_of_abortion&amp;diff=30"/>
		<updated>2014-09-26T18:31:03Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot; Primeros auxilios en caso de desangre por aborto. http://transhackfeminist.noblogs.org/post/2014/08/04/taller-primeros-auxilio-en-caso-de-aborto-y-derrame/      Miramos estad...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Primeros auxilios en caso de desangre por aborto.&lt;br /&gt;
http://transhackfeminist.noblogs.org/post/2014/08/04/taller-primeros-auxilio-en-caso-de-aborto-y-derrame/&lt;br /&gt;
&lt;br /&gt;
    Miramos estadisticas en el mundo comparacion entre españa, turkia y chile &amp;gt; https://es.wikipedia.org/wiki/Anexo:Legislaci%C3%B3n_del_aborto&lt;br /&gt;
&lt;br /&gt;
    Metrorrhagia (metro = womb, -rrhagia = excessive flow[1]) is uterine bleeding at irregular intervals, particularly between the expected menstrual periods&lt;br /&gt;
&lt;br /&gt;
    en chile: misoprostol https://en.wikipedia.org/wiki/Misoprostol&lt;br /&gt;
&lt;br /&gt;
    http://www.medicationabortion.com/misoprostol/index.html&lt;br /&gt;
&lt;br /&gt;
    http://medicationabortion.com/Spanish/misoprostol/index.html&lt;br /&gt;
&lt;br /&gt;
    http://www.womenonwaves.org/en/page/597/misoprostol-cytotec-pastilla-aborto&lt;br /&gt;
&lt;br /&gt;
    http://www.abortoseguro.com/&lt;br /&gt;
&lt;br /&gt;
    En un pais donde el aborto es ilegal (como en chile) aunque uses una técnica farmacologica, existe el miedo de que &amp;quot;te descubran&amp;quot;, por medio de una biopsia. po ejemplo el misoprostol se mete en el coño (aki es detectable en biopsia) pero existen técnicas como metertela en la encia (dificil de detectar)&lt;br /&gt;
&lt;br /&gt;
    Aun así el miedo a ser descubierta, que la medicina te a  pillar es muy potente&lt;br /&gt;
&lt;br /&gt;
    ¿llamar ambulancia en un lugar que es delito?&lt;br /&gt;
&lt;br /&gt;
    tecnicas uterinas por ineccion&lt;br /&gt;
&lt;br /&gt;
    fono naborto en chile&lt;br /&gt;
&lt;br /&gt;
    http://www.publimetro.cl/nota/fono-aborto-desata-escandalo-e-indignacion-en-organizaciones-pro-vida/bNQieC!523510/&lt;br /&gt;
&lt;br /&gt;
    http://www.freelists.org/post/co_inspiracion/Fono-Aborto-mujeres-por-el-derecho-a-la-informacin&lt;br /&gt;
&lt;br /&gt;
    https://www.womenonwaves.org/en/page/932/media-coverage-chile&lt;br /&gt;
&lt;br /&gt;
    http://menstruar.blogspot.com.es/2011/07/aborto-en-chile.html&lt;br /&gt;
&lt;br /&gt;
    http://www.abortoinformacionsegura.blogspot.com.es/?zx=6eea9b08a568cb4b&lt;br /&gt;
&lt;br /&gt;
    fabricar una pildora con anticonceptivos (una bomba)&lt;br /&gt;
&lt;br /&gt;
    http://www.plannedparenthood.org/esp/temas-de-salud/aborto/la-pildora-abortiva-aborto-inducido-por-medicamentos/&lt;br /&gt;
&lt;br /&gt;
    http://www.aciprensa.com/vida/efectos.htm&lt;br /&gt;
&lt;br /&gt;
    http://es.rudd-o.com/archivos/como-hacer-tu-propia-pastilla-o-pildora-del-dia-despues-o-siguiente&lt;br /&gt;
&lt;br /&gt;
    http://www.clinicasabortos.com/aborto-con-pastillas/sec15&lt;br /&gt;
&lt;br /&gt;
    tipos de hemorragia: arterial, capilar, venosa&lt;br /&gt;
&lt;br /&gt;
Revisión tecnicas (pegaremos el texto que tiene rox)&lt;br /&gt;
red: http://directa.cat/noticia/creada-xarxa-frederica-montseny-pel-dret-lavortament-lliure-segur-lestranger&lt;br /&gt;
relacionado: &lt;br /&gt;
&lt;br /&gt;
    http://transhackfeminist.noblogs.org/post/2014/07/24/gynepunk-biolab-laboratorio-de-diagnosis-lowcost/&lt;br /&gt;
&lt;br /&gt;
    http://mariallopisdesnuda.com/2014/06/sobre-la-guia-para-el-aborto-espontaneo/&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Experimental_Fanzinoteka/_Experimental_fanzinotheque&amp;diff=29</id>
		<title>Experimental Fanzinoteka/ Experimental fanzinotheque</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Experimental_Fanzinoteka/_Experimental_fanzinotheque&amp;diff=29"/>
		<updated>2014-09-26T18:30:26Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;EXperimental Fanzinoteka [nodo rizoma]  http://transhackfeminist.noblogs.org/post/2014/07/25/fanzinoteca-experimental-nodo-rizoma/ http://transhackfeminist.noblogs.org/post/20...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;EXperimental Fanzinoteka [nodo rizoma]&lt;br /&gt;
&lt;br /&gt;
http://transhackfeminist.noblogs.org/post/2014/07/25/fanzinoteca-experimental-nodo-rizoma/&lt;br /&gt;
http://transhackfeminist.noblogs.org/post/2014/08/07/feminist-zine-repository/&lt;br /&gt;
&lt;br /&gt;
    &amp;quot;If you go home with someone and they don't have books, don't fuck them.&amp;quot; John Waters&lt;br /&gt;
&lt;br /&gt;
    “Los libros y las prostitutas entrecruzan el tiempo. Dominan la noche como el día y el día como la noche.”&lt;br /&gt;
&lt;br /&gt;
o (Dirección única)&lt;br /&gt;
&lt;br /&gt;
    Every passion borders on the chaotic, but the collector's passion borders on the chaos of memories.&lt;br /&gt;
&lt;br /&gt;
Walter Benjamin&lt;br /&gt;
// Zine repositories &lt;br /&gt;
&lt;br /&gt;
    http://lecrips.net/l/menu.htm&lt;br /&gt;
&lt;br /&gt;
    http://www.spunk.org/cat-us/geekgirl.html&lt;br /&gt;
&lt;br /&gt;
    http://zinewiki.com&lt;br /&gt;
&lt;br /&gt;
    http://www.grrrlzines.net&lt;br /&gt;
&lt;br /&gt;
    http://www.jura.org.au/files/jura/Mutiny70_Web-2.pdf&lt;br /&gt;
&lt;br /&gt;
    http://anarchalibrary.blogspot.com.es&lt;br /&gt;
&lt;br /&gt;
    http://www.sproutdistro.com/&lt;br /&gt;
&lt;br /&gt;
    http://www.fanzino.org/&lt;br /&gt;
&lt;br /&gt;
    http://hysteria.mx/&lt;br /&gt;
&lt;br /&gt;
    http://publicacoes.midiatatica.info/&lt;br /&gt;
&lt;br /&gt;
    http://www.grannegro.org/home.html&lt;br /&gt;
&lt;br /&gt;
    http://www.londonzinesymposium.org.uk/&lt;br /&gt;
&lt;br /&gt;
    http://perrogordo.cl/fanzines/&lt;br /&gt;
&lt;br /&gt;
    http://thatsnotonline.tumblr.com/post/4183294981/zines&lt;br /&gt;
&lt;br /&gt;
    http://lazinefest.tumblr.com/&lt;br /&gt;
&lt;br /&gt;
    http://geeksandfreakszine.com/&lt;br /&gt;
&lt;br /&gt;
    http://feriadefanzines.wordpress.com/talleres/&lt;br /&gt;
&lt;br /&gt;
    http://paperplayings.blogspot.com.es/&lt;br /&gt;
&lt;br /&gt;
    http://wemakezines.ning.com/&lt;br /&gt;
&lt;br /&gt;
    http://missogina.perrogordo.cl/fanzine-contrasexualidad-dildotecnia/&lt;br /&gt;
&lt;br /&gt;
// Libraries&lt;br /&gt;
&lt;br /&gt;
    http://www.bibliotecafragmentada.org&lt;br /&gt;
&lt;br /&gt;
    http://www.etnassoft.com/biblioteca/&lt;br /&gt;
&lt;br /&gt;
    http://www.rebelion.org/seccion.php?id=24&lt;br /&gt;
&lt;br /&gt;
    http://www.cholonautas.edu.pe&lt;br /&gt;
&lt;br /&gt;
    http://revistarebeldia.org/&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=HerStory&amp;diff=28</id>
		<title>HerStory</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=HerStory&amp;diff=28"/>
		<updated>2014-09-26T18:29:52Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;Lelacoders: An animation about the HerStory of computer sciences  Why:  For decades, research on gender and technology has highlighted the under-representation of women in tec...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Lelacoders: An animation about the HerStory of computer sciences&lt;br /&gt;
&lt;br /&gt;
Why:&lt;br /&gt;
&lt;br /&gt;
For decades, research on gender and technology has highlighted the under-representation of women in technology. Although sub-research on the field studying women contributing to free software and hackers cultures is very limited, it also points to women’s low participation rates. However, behind these figures and the discourses that accompany them, other, hidden situations may appear: on the one hand, the existence of some women who do participate and might have been invisible before, on the other the widespread assumption that women are not interested or have an innate inability to engage with technology on a deeper level.&lt;br /&gt;
&lt;br /&gt;
The aim of this animation is to actively oppose the prejudice that there are no significant women behind the development of sciences and technologies. This is the result of a systematic negation and invisibility of women in those specific histories. This drives to a lack of role models which perpetuate the women off-the-loop relation with ICT. Finding and making visible those stories is an important element to re-appropriate historical and collective memory and enable the emergence of new imaginaries which we hoped to be very much radical and feminists!&lt;br /&gt;
&lt;br /&gt;
How To:&lt;br /&gt;
&lt;br /&gt;
One very nice way of interacting with this animation is by projecting it with a beamer and enjoy the PD patch, its rhythm, the music and the enormous input of information it carries. It can be also used into many other different settings, for a concert, an installation very DIT, or as food for thought to engage people interested in technologies and their social, political, educational meanings into conversations about the visible and invisible gender divisions operating into our equal access to technologies, its understanding and development.&lt;br /&gt;
&lt;br /&gt;
The animation format was chosen as a way of further exploring the possibilities offered by PureData (a free visual programming language) and how as a media it could feet our desire to spread this cyberfeminist work. We also understand that the first outcome of its visioning might be confusion :-). However, its primary purpose is not to be a videotutorial or a self-containing educational resource, it first aims at creating interest curiosity, surprise and we hope interest. Departing from confusion caused by too much data, people should be able to go towards a more documented understanding of women contribution to CS and the related social and political issues related to gender divisions inside IT contexts.&lt;br /&gt;
&lt;br /&gt;
Process:&lt;br /&gt;
&lt;br /&gt;
As said par Chris Marker “Luck has intuitions that should not be taken for coincidences”. Two years ago I was reviewing a beautiful visualisation made by normal c-alas and based on the text of VNS matrix “the bitch mutant manifesto”. This is how we came to work together in building this animation which first main task consisted in compiling images for the animation of this Her Story.&lt;br /&gt;
&lt;br /&gt;
Meanwhile researching the HerStory, an email was forwarded from a friend of a friend involved in communitarian radio broadcasting in Oaxaca (Mexico) and which was putting up a publication of women experiences working or developing new ICT. She was also looking for latin american and african women and she was having a hard time to find this information on  internet. There is a lack of coverage of those contributions in the history of science, translations but also of indexing and linking between the few contents available, which drive to a cyberfeminist field mainly composed by disconnected islands of knowledge. Even though this chronology is partial and subjective, it is important to open those lines of research and share more knowledge inside common free culture repositories such as wikipedia and have them linked with open data hosted in free platforms.&lt;br /&gt;
&lt;br /&gt;
Next steps:&lt;br /&gt;
Translation of the texts (see below) to spanish, catalan, french, portuguese.&lt;br /&gt;
Exportation of the animations into new videos clips.&lt;br /&gt;
&lt;br /&gt;
Thanks to:&lt;br /&gt;
Normal c-alas for programming the patch, developing the animation, researching and editing images and being amazingly motivated and creative&lt;br /&gt;
Foockinho for patiently editing the numerous images gathered&lt;br /&gt;
Electroputas for the music: Ella  (RmX ton Once to Open - Ella Fitzgeralt - from the first demo cd / eLeCTRopUtaS YEAR 2005) and thanks also to Osmozer / JT25 for the live music&lt;br /&gt;
b01 for making the PD run and for the video export&lt;br /&gt;
Reni hofmüller for the translation to german of the animation&lt;br /&gt;
IOhannes m zmolnig for making the PD run for the Ministry of hacking&lt;br /&gt;
Videohackers for the graphic target&lt;br /&gt;
Sydney Padua for letting us use the wonderful images of her comic on Ada Lovelace&lt;br /&gt;
Wikipedia and more specifically the Women in computing article&lt;br /&gt;
Esao Andrews (Young Mary Shelley)&lt;br /&gt;
The women are there, Computer Science for fun, annual issue 2&lt;br /&gt;
Margaret Sarah Carpenter (Ada Lovelace portrait)&lt;br /&gt;
J. Howard Miller's (We Can Do It! poster)&lt;br /&gt;
MichigansWallofFame (Rosie tech)&lt;br /&gt;
Computer History Museum  (ENIAC)&lt;br /&gt;
The Ada project&lt;br /&gt;
Anita Borg Institute for Women and Technology fortheir Profiles of Technical Women: Famous Women in Computer Science&lt;br /&gt;
Dr. James E. Brittain&lt;br /&gt;
Masolino&lt;br /&gt;
Utterlyelastic's Blog&lt;br /&gt;
Computerhope.com&lt;br /&gt;
Vintage Computer Festival website&lt;br /&gt;
Computerhistory.org&lt;br /&gt;
Lisa Foo&lt;br /&gt;
American Institute of Physics (Henrietta Swan Leavitt)&lt;br /&gt;
Amaya Rodrigo, primera mujer europea en desarrollar Debian, article by Mercé Molist (http://www.nodo50.org/mujeresred/spip.php?article650)&lt;br /&gt;
And last but not least, The commons and the public domain&lt;br /&gt;
&lt;br /&gt;
Text of the timeline used in the animation:&lt;br /&gt;
&lt;br /&gt;
360 AD: Hypatia&lt;br /&gt;
&lt;br /&gt;
First well-documented woman in mathematics. Head of the Platonist school at Alexandria %44 taught philosophy and astronomy. Her contributions to geometry and astrometry were instrumental in developing the planesphere and the astrolabe&lt;br /&gt;
&lt;br /&gt;
1818:Mary Shelley&lt;br /&gt;
&lt;br /&gt;
Wrote the first science novel on artificial intelligence: Frankestein&lt;br /&gt;
&lt;br /&gt;
1842: Ada Lovelace&lt;br /&gt;
&lt;br /&gt;
Considered the world's first computer programmer. Mathematician known for her work on Charles Babbage's Analytical Engine%44 recognized as the first algorithm intended to be processed by a machine&lt;br /&gt;
&lt;br /&gt;
1856: Florence Nightingale&lt;br /&gt;
&lt;br /&gt;
Visual presentation of information and statistical graphics. Nightingale rose diagram illustrate seasonal sources of patient mortality in the military field hospital she managed&lt;br /&gt;
&lt;br /&gt;
1893: Henrietta Swan Leavitt&lt;br /&gt;
&lt;br /&gt;
She joined the Harvard &amp;quot;computers&amp;quot;: a group of women engaged in the production of astronomical data at Harvard. Her work was instrumental in discovery of the cepheid variable stars%44 evidence for the expansion of the universe&lt;br /&gt;
&lt;br /&gt;
1877 - 1919: Harvard Computers women&lt;br /&gt;
&lt;br /&gt;
The director of the Harvard Observatory hired women as skilled workers to process astronomical data.&lt;br /&gt;
&lt;br /&gt;
Williamina Fleming Annie Jump Cannon Henrietta Swan Leavitt and Antonia Maury&lt;br /&gt;
&lt;br /&gt;
1919: Edith Clarke&lt;br /&gt;
&lt;br /&gt;
Electrical engineering - MIT - Electrical power system analysis.&lt;br /&gt;
&lt;br /&gt;
1926: Grete Hermann&lt;br /&gt;
&lt;br /&gt;
Foundations of computerized algebra and quantum mechanics&lt;br /&gt;
&lt;br /&gt;
1941: Hedy Lamar&lt;br /&gt;
&lt;br /&gt;
Patented a system basis for spread-spectrum communication technologies&lt;br /&gt;
&lt;br /&gt;
1943: Rosie the Riveter&lt;br /&gt;
&lt;br /&gt;
1941 only 1% of aviation employees were women and in 1943 they comprise an estimated 65% of the total. Of the 16.000.000 women employed over a quarter were in war industries.&lt;br /&gt;
&lt;br /&gt;
1943: Operators at Bletchley Park - The Colossus computers used by British codebreakers&lt;br /&gt;
&lt;br /&gt;
1943: Manhattan Project - Oak Ridge - Calutron -Wives of scientists were organized as &amp;quot;computers&amp;quot; on the Manhattan Project&lt;br /&gt;
&lt;br /&gt;
1943: Gertrude Blanch - Led the Mathematical Tables Project group throughout the war.&lt;br /&gt;
&lt;br /&gt;
1945: Grace Murray Hopper&lt;br /&gt;
Programmer of COBOL and the first compiler - Coined the term 'debugging'&lt;br /&gt;
&lt;br /&gt;
1946: ENIAC&lt;br /&gt;
&lt;br /&gt;
Betty Jennings - Betty Snyder - Fran Bilas, Kay McNulty - Marlyn Wescoff and Ruth Lichterman were the original programmers of the ENIAC, the first electronic general-purpose computer&lt;br /&gt;
&lt;br /&gt;
1949:Evelyn Boyd Granville - PhD in mathematics - Worked for IBM analyzing orbits and computer procedures&lt;br /&gt;
&lt;br /&gt;
1950: Ida Rhodes&lt;br /&gt;
&lt;br /&gt;
Designed the C-10 language used to calculate the census and the original computer used for the Social Security Administration&lt;br /&gt;
&lt;br /&gt;
1962:Jean E. Sammet&lt;br /&gt;
&lt;br /&gt;
Developped the FORMAC language and wrote about the history and categorisation of programming languages&lt;br /&gt;
&lt;br /&gt;
1965: Mary Allen Wilkes&lt;br /&gt;
&lt;br /&gt;
Computer programmer and hardware engineer and the first to use a computer in a private home&lt;br /&gt;
&lt;br /&gt;
1965: Sister Mary Kenneth Keller&lt;br /&gt;
&lt;br /&gt;
1st American woman PhD in Computer Sciences and contributed to BASIC development&lt;br /&gt;
&lt;br /&gt;
1966: Margaret R. Fox&lt;br /&gt;
&lt;br /&gt;
Chief of the Office of Computer Information and involved in the Association for Computing Machinery&lt;br /&gt;
&lt;br /&gt;
1971: Dr. Erna Schneider Hoover&lt;br /&gt;
&lt;br /&gt;
Mathematician inventor of a computerized telephone switching method preventing system overloads&lt;br /&gt;
&lt;br /&gt;
1972: Adele Goldberg&lt;br /&gt;
&lt;br /&gt;
Computer scientist Development of Smalltalk-80 and other object oriented programming&lt;br /&gt;
&lt;br /&gt;
1972: Karen Spärck Jones&lt;br /&gt;
&lt;br /&gt;
A pioneer of information retrieval and natural language processing - She said that &amp;quot;Computing is too important to be left to men&amp;quot;&lt;br /&gt;
&lt;br /&gt;
1979: Carol Shaw&lt;br /&gt;
&lt;br /&gt;
Video game designer of Polo game, 3-D Tic-Tac-Toe and River Raid&lt;br /&gt;
&lt;br /&gt;
1984: Susan Kare&lt;br /&gt;
&lt;br /&gt;
Graphic designer of many of the interface elements for the Apple Macintosh&lt;br /&gt;
&lt;br /&gt;
1985: Radia Perlman&lt;br /&gt;
&lt;br /&gt;
Software designer and network engineer and inventor of the spanning-tree protocol&lt;br /&gt;
&lt;br /&gt;
1985: Donna Haraway&lt;br /&gt;
&lt;br /&gt;
Published &amp;quot;A Cyborg Manifesto: Science Technology and Socialist-Feminism in the Late Twentieth Century&amp;quot;&lt;br /&gt;
&lt;br /&gt;
1989: Frances E. Allen&lt;br /&gt;
&lt;br /&gt;
First woman to win the Turing Award&lt;br /&gt;
&lt;br /&gt;
1993: Shafi Goldwasser&lt;br /&gt;
&lt;br /&gt;
Artificial Intelligence Laboratory and co-inventor of zero-knowledge proofs&lt;br /&gt;
&lt;br /&gt;
1993: Barbara Liskov and Jeannette Wing&lt;br /&gt;
&lt;br /&gt;
Developed the Liskov substitution principle and won the Turing Prize in 2008&lt;br /&gt;
&lt;br /&gt;
1994: Sally Floyd&lt;br /&gt;
&lt;br /&gt;
Her work on Internet congestion control is one of the top-ten most cited researches in CS&lt;br /&gt;
&lt;br /&gt;
1997: Anita Borg&lt;br /&gt;
&lt;br /&gt;
She developed an email and Web-based system for communicating in virtual communities.&lt;br /&gt;
&lt;br /&gt;
Founded the Institute for Women and Technology&lt;br /&gt;
&lt;br /&gt;
1998: LinuxChix founded by Deb Richardson&lt;br /&gt;
&lt;br /&gt;
An organisation for women who use Linux and women and men who want to support women in computing&lt;br /&gt;
&lt;br /&gt;
2002: Valerie Aurora&lt;br /&gt;
&lt;br /&gt;
Published How to encourage women in linux and she is a co-founder of the Ada Initiative&lt;br /&gt;
&lt;br /&gt;
2003: Ellen Spertus&lt;br /&gt;
&lt;br /&gt;
App Inventor for Android&lt;br /&gt;
&lt;br /&gt;
2004: Debian women&lt;br /&gt;
&lt;br /&gt;
Promotion of women's involvement in the Debian Project&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=UpStage,_plataforma_de_codigo_abierto_para_cyberperformaces/Upstage,_open_source_platform_for_cyberperformance&amp;diff=27</id>
		<title>UpStage, plataforma de codigo abierto para cyberperformaces/Upstage, open source platform for cyberperformance</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=UpStage,_plataforma_de_codigo_abierto_para_cyberperformaces/Upstage,_open_source_platform_for_cyberperformance&amp;diff=27"/>
		<updated>2014-09-26T18:29:21Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;UPSTAGE  (Helen already started the presentation, i'm late, sorry) UPSTAGE (works with flash / shockwave plugin) create media, upload and then play with it Upstage basically t...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;UPSTAGE&lt;br /&gt;
&lt;br /&gt;
(Helen already started the presentation, i'm late, sorry)&lt;br /&gt;
UPSTAGE&lt;br /&gt;
(works with flash / shockwave plugin)&lt;br /&gt;
create media, upload and then play with it&lt;br /&gt;
Upstage basically takes the window as a stage&lt;br /&gt;
Like in theater, you can be multi players, &lt;br /&gt;
http://upstage.org.nz:8083/stages/walkthrough ---------&amp;gt; to sign in&lt;br /&gt;
real time working with media (images, animation, audio, livestream, live drawing...) made by several ppl &amp;amp; uploaded before&lt;br /&gt;
////// audio files have to be mp3 //////&lt;br /&gt;
chat window for the audience ---&amp;gt; reactions &amp;amp; discussions&lt;br /&gt;
from the inside : everybody see the same things &lt;br /&gt;
there's a voice also&lt;br /&gt;
a drawing tool&lt;br /&gt;
[EXPLORING MOMENT]&lt;br /&gt;
everyone is invited to test, upload media &amp;amp; try&lt;br /&gt;
1 &lt;br /&gt;
creating a stage : http://upstage.org.nz:8083/admin/workshop/stage&lt;br /&gt;
uploading : http://upstage.org.nz:8083/admin/workshop/mediaupload&lt;br /&gt;
//// you can delete a stage but the media won't delete /////&lt;br /&gt;
evrybody has access to all the media content, so you don't have an avatar to represent you (you can have one but everybody can control it)&lt;br /&gt;
creative commons policy&lt;br /&gt;
try to make your media as small as u can when u upload, so it doesnt take so much time for&lt;br /&gt;
limit : 1Mb but ask Helen if u need more&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=GYNEpunk:_Autonomous_ginecologyLAB&amp;diff=26</id>
		<title>GYNEpunk: Autonomous ginecologyLAB</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=GYNEpunk:_Autonomous_ginecologyLAB&amp;diff=26"/>
		<updated>2014-09-26T18:28:53Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;GYNEPUNK WE CAN DO IT ! Decolonizacion corporal http://transhackfeminist.noblogs.org/post/2014/07/24/gynepunk-biolab-laboratorio-de-diagnosis-lowcost/ http://gynepunk.hotglue....&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;GYNEPUNK&lt;br /&gt;
WE CAN DO IT ! Decolonizacion corporal&lt;br /&gt;
http://transhackfeminist.noblogs.org/post/2014/07/24/gynepunk-biolab-laboratorio-de-diagnosis-lowcost/&lt;br /&gt;
http://gynepunk.hotglue.me/&lt;br /&gt;
http://gynepunk.tumblr.com/&lt;br /&gt;
hackeria link ??&lt;br /&gt;
piratepad link ??&lt;br /&gt;
INTRO / SPELLING :&lt;br /&gt;
&amp;quot;No quiero entrar en sus templos higienistas, en sus cárceles veladas, en sus fabricas de homologación corporal. quiero herejía glandular, akelarres gynepunks, pócimas abortivas DIY, parterxs pandilleras, abortos de purpurina, placenta derramada en las esquinas, hackear técnicas analíticas, biolabs efímeros, laboratorios auto-gestionados, sesiones pactadas de enfermería hitech, batas negras, batas a cuadros… Auto-donarnos y extraernos nuestra sangre para lanzarla como río volcánico furioso de nuestra ira en la puerta del maldito y repugnante parlamento!!! gynepunk es un gesto precisom determinado y certero para desprender la excesiva dependencia de las estructuras anquilosadas de &amp;quot;la salud&amp;quot; estatal y hegemónica.&amp;quot;&lt;br /&gt;
The silver thread : theater piece about the life of Anarcha&lt;br /&gt;
Incidents in the life of a slave girl&lt;br /&gt;
Amaranta Gomez &lt;br /&gt;
LA ciencia es experimentaron, conocimiento compartido, creatividad y curiosidad. La tecnología que se use moldeara el tipo de ciencia que la use, y los laboratorios que trafican con nuestra salud son un lobby más: farmacéuticas, multinacionales y armamentistas, flipa.&lt;br /&gt;
gynepunk tiene como objetivo visionario*, que broten laboratorios DIY-DIT de diagnosis accesible y extrema experimentación debajo de las piedras o en ascensores, ya sea en un espacio fijo o en nomadismo de laboratorios móviles. Y poder hacer a destajo, antojo e intensidad cultivos, análisis de fluidos, biopsias, PAPs, sintetizar hormonas, exámenes de sangre, de orina, VIH, de lo que haga falta! consrtuir, hackear cacharrukos de ultrasonido, endoscopias, ecografias!. Todo esto en potencia elevada a re-vistar conocimientos sobre hierbas, pócimas sumergidas, generar superavit de lubricantes DIY, anticoncepción y técnicas viscerales como la extracción menstrual.&lt;br /&gt;
gynepunk se basa en metodología científica y conocimiento desde la experiencia de cada cuerpo, y por ello es vitál la documentación, la memoria, como sea! tesoro visual, mina sonora, cabinet biológico, vivero microbiológico, semillero online, mensajera en papel, asi otrxs gynepunks fermentaran y mutaran avanzando en movimientos explosivos y expansivos a la radicalidad experimental, al perfeccionamiento colectivo, a compartir y diseminar infinitos pandemoniums.&lt;br /&gt;
MANUAL DE GINECOLOGIA NATURAL&lt;br /&gt;
http://ginecologianatural.wordpress.com/about/&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Open_Street_Map_Mapping_Party&amp;diff=25</id>
		<title>Open Street Map Mapping Party</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Open_Street_Map_Mapping_Party&amp;diff=25"/>
		<updated>2014-09-26T18:27:37Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;http://transhackfeminist.noblogs.org/post/2014/07/24/openstreetmap-mapping-party/ Maps as: 1. technical instruments, used for visualisation 2. political tools - i.e. map of fr...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://transhackfeminist.noblogs.org/post/2014/07/24/openstreetmap-mapping-party/&lt;br /&gt;
Maps as:&lt;br /&gt;
1. technical instruments, used for visualisation&lt;br /&gt;
2. political tools - i.e. map of freedom and restriction, showing power&lt;br /&gt;
3. artwork&lt;br /&gt;
4. social products&lt;br /&gt;
- expert vs collaborative mapping&lt;br /&gt;
- authoritative vs. playful&lt;br /&gt;
OSM:&lt;br /&gt;
    - personal experience&lt;br /&gt;
    - local / tacit knowledge&lt;br /&gt;
    - memories&lt;br /&gt;
    - identities&lt;br /&gt;
    - belongings&lt;br /&gt;
    - emotions&lt;br /&gt;
    - ideologies&lt;br /&gt;
    - philosophies&lt;br /&gt;
    &lt;br /&gt;
OSM free software started 10 years ago by Steve Coast&lt;br /&gt;
- social ingagement, mapping parties&lt;br /&gt;
- humanitarian mapping - crisis mapping (mapping resources, mapping in case of disasters), OSM for accesibilities&lt;br /&gt;
- fast updates: new shops, new countries, new city plans&lt;br /&gt;
- MORE MAPPERS ARE NEEDED&lt;br /&gt;
- knowledge making - observing, classifying, sorting things out, linking, socialising&lt;br /&gt;
- mapping trees, animals, postcodes&lt;br /&gt;
- so not copy data from google - copyright, data quality&lt;br /&gt;
- importancy of mapping with local people&lt;br /&gt;
- politicysing the current state of OSM: CCTV, benches, car parks, recycling, parks - WHAT'S MISSING?&lt;br /&gt;
- MAPPING TIPS:&lt;br /&gt;
&lt;br /&gt;
    - photo mapping - reference based, matching photo and camera data&lt;br /&gt;
&lt;br /&gt;
- HOW TO MAP:&lt;br /&gt;
    - login to https://www.openstreetmap.org&lt;br /&gt;
    - different editors&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Tacticas_Feministas_en_la_red/Feminist_Tactis_in_the_Net&amp;diff=24</id>
		<title>Tacticas Feministas en la red/Feminist Tactis in the Net</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Tacticas_Feministas_en_la_red/Feminist_Tactis_in_the_Net&amp;diff=24"/>
		<updated>2014-09-26T18:26:32Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;http://transhackfeminist.noblogs.org/post/2014/07/25/tacticas-feministas-en-la-red-feminists-tactics-in-the-net/ Sharing practices e.g.,  Herstory www.donestech.net Photo of M...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://transhackfeminist.noblogs.org/post/2014/07/25/tacticas-feministas-en-la-red-feminists-tactics-in-the-net/&lt;br /&gt;
Sharing practices&lt;br /&gt;
e.g., &lt;br /&gt;
Herstory&lt;br /&gt;
www.donestech.net&lt;br /&gt;
Photo of Marina http://en.wikipedia.org/wiki/Marina_Ginest%C3%A0&lt;br /&gt;
ATGENDER http://www.atgender.eu/  &lt;br /&gt;
Most of the subscribers to the online courses are from South America.   &lt;br /&gt;
Harassmap - geolocalise violence in Middle East countries (in English as well as in Arabic) (developed by women) &lt;br /&gt;
http://harassmap.org/en/&lt;br /&gt;
note: different kinds of violence&lt;br /&gt;
YL: looks a bit like Ushahidi - &lt;br /&gt;
http://www.ushahidi.com/&lt;br /&gt;
women on waves (abortion help)&lt;br /&gt;
http://www.womenonwaves.org/&lt;br /&gt;
Online magazines:&lt;br /&gt;
    &lt;br /&gt;
http://www.pikaramagazine.com/&lt;br /&gt;
Context in Spain: &amp;quot;neomachismos&amp;quot; https://www.diagonalperiodico.net/libertades/neomachismos-nuevos-ataques-nuevas-respuestas.html&lt;br /&gt;
http://memesfeministas.wordpress.com/&lt;br /&gt;
All the info of the presentation is (in Spanish only :( ) here: Kit de formación: Género, TIC y Activismo http://www.e-igualdad.net/iniciativas/banco-experiencias/sector-tic/kit-formaci%C3%B3n-g%C3%A9nero-tic-activismo&lt;br /&gt;
---- MORE EXAMPLES&lt;br /&gt;
&amp;quot;everyday sexism&amp;quot;&lt;br /&gt;
UN against Google Autocomplete Campaign&lt;br /&gt;
Turkey - Women LOL (laugh out loud) campaign&lt;br /&gt;
OccupyWallSt.org - A web platform create by transwomen and queer within the Occupy Wall Street Movement &lt;br /&gt;
To know more: http://dpi.studioxx.org/en/no/28-gendered-cultures-internet/feminist-queer-and-trans-online-and-offline-praxis (Short non-academic article)&lt;br /&gt;
     http://ojs.meccsa.org.uk/index.php/netknow/article/view/307 (an open access academic journal)&lt;br /&gt;
     &lt;br /&gt;
     Feminist Frequency: http://www.feministfrequency.com/&lt;br /&gt;
     &lt;br /&gt;
     Ada Camp: http://adacamp.org/ (they have an open call for an Ada Camp Berlin) - question here is: is that a strategy to go to such events where you are funded by big corporations (such as Google, etc.)?&lt;br /&gt;
     &lt;br /&gt;
     Feminist Bat Signal on twitter: https://twitter.com/FemBatSignal  Are trolls troubling you? Getting harassed online? Turn on the @FemBatSignal and get help from feminists and allies!&lt;br /&gt;
     &lt;br /&gt;
     FemTechNet:http://femtechnet.newschool.edu/ &lt;br /&gt;
     &lt;br /&gt;
     #YesAllWomen:https://en.wikipedia.org/wiki/YesAllWomen  &lt;br /&gt;
     &lt;br /&gt;
http://machosalahoguera.wordpress.com/&lt;br /&gt;
http://gynandco.wordpress.com/&lt;br /&gt;
An example from Pakistan is Bolo Bhi:  Bolo Bhi means ‘Speak up’, in Urdu. We are a  not-for-profit geared towards advocacy, policy and research in the areas  of gender rights, government transparency, internet access, digital  security and privacy. We are a team of individuals with diverse  backgrounds who are passionate about the same causes and believe it is  crucial to bridge the gap between rights advocates, policy makers, media  and citizens. It is by bridging this gap that one can move ahead to  chart a way forward and resolve issues through consensus.&lt;br /&gt;
They have - among other things - a tool called &amp;quot;Bolo Bhi Minority Report: Mapping Instances Of Sectarian Violence&amp;quot; which is similar to the harras map&lt;br /&gt;
  http://bolobhi.org/activities/our-projects/bolo-bhi-minority-report-mapping-instances-of-sectarian-violence/&lt;br /&gt;
  http://bolobhi.org/&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Cyborg_Romanticism&amp;diff=23</id>
		<title>Cyborg Romanticism</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Cyborg_Romanticism&amp;diff=23"/>
		<updated>2014-09-26T18:25:21Z</updated>

		<summary type="html">&lt;p&gt;Thf: Created page with &amp;quot;http://transhackfeminist.noblogs.org/post/2014/07/24/critical-debate-cyborg-romanticism-and-futurist-fetisch-ization/ //init. using this as starting point as debate:  Xlterres...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;http://transhackfeminist.noblogs.org/post/2014/07/24/critical-debate-cyborg-romanticism-and-futurist-fetisch-ization/&lt;br /&gt;
//init.&lt;br /&gt;
using this as starting point as debate: &lt;br /&gt;
Xlterrestrials aboout THF! { Having  investigated the cyborg ideologies out there in CiTiZEN KiNO #31,  Xlterrestrials are still a Little unsure about Cyborgian romanticism and  futurist fetisch-ization, which in our view is leading to further  exploitation and degradation of our ‘natural’ environments, and to a  potentially techno-fascist climate, but the nice artwork and ideas for  Transhackfeminist meet IS alluring… and undoubtedly ENGAGED! }&lt;br /&gt;
http://xlterrestrials.org/plog/?p=12659&lt;br /&gt;
CiTiZEN KiNO #31: I’m A Cyborg, But That’s NOT OK !http://xlterrestrials.org/plog/?p=11659&lt;br /&gt;
pirate pad notes debate I’m A Cyborg, But That’s NOT OK !: http://piratepad.net/r3JWrjInYP&lt;br /&gt;
// Reazioni e antropotecniche di sopravvivenza - ippolita.net&lt;br /&gt;
related also to the ippolita critique &lt;br /&gt;
Le critiche alle tecnoburocrazie si possono agevolmente applicare  all'informatica del dominio, denunciata da Donna Haraway, «A Cyborg  Manifesto: Science, Technology, and Socialist-Feminism in the Late  Twentieth Century,» in Simians, Cyborgs and Women: The Reinvention of  Nature, New York, Routledge, 1991, p. 161. I sistemi cumulativi  gerarchici tendono a sviluppare modelli sociali concentrazionari a  prescindere dalle epoche. Le competenze personali richieste per  contribuire a tali sistemi decrescono con l'aumentare del potere  tecnico. In particolare, si veda l'analisi del sistema sovietico in  Cornelius Castoriadis, La societé bureaucratique, Bourgois, Paris, 1990&lt;br /&gt;
http://www.ippolita.net/it/libro/reazioni-e-antropotecniche-di-sopravvivenza&lt;br /&gt;
// fetishism - fetishisation - john holloway&lt;br /&gt;
then use the fetish analisis of holloway&lt;br /&gt;
The concept of fetishism is concerned with the explosion of power inside us, not as something tha is distinct from the separation of doing and done (as in the concepts of ‘ideology’ and ‘hegemony’), but as something that is integral to that separation. That separation does not just divide capitalists from workers, but explodes inside us, shaping every aspect of what we do and what we think, transforming every breath of our lives into a moment of class struggle. The problem of why revolution has not happened is not a problem of ‘them’, but a problem of a fragmented ‘us’.&lt;br /&gt;
http://www.johnholloway.com.mx/2011/07/30/class-and-classification/&lt;br /&gt;
http://libcom.org/library/chapter-4-fetishism&lt;br /&gt;
http://libcom.org/library/chapter-5-fetishism-fetishisation&lt;br /&gt;
// CybORG&lt;br /&gt;
A cyborg is [...] a hybrid of machine and organism, a creature of social reality as well as a creature of fiction.&lt;br /&gt;
Donna Haraway (1991: 149)&lt;br /&gt;
// chela sandoval - Nuevas ciencias. Feminismo cyborg&lt;br /&gt;
to go then to review feminist cyborg imaginaries&lt;br /&gt;
Sin embargo, no deja de resultar significativo que los teóricos de la globalización se comprometan ahora con la introducción de una política «cyborg» opositiva como si esta política hubiera emergido únicamente con el advenimiento de la tecnología electrónica, y no como resultado de una conciencia en oposición desarrollada bajo formas previas de dominación.&lt;br /&gt;
El cyborg de Haraway es la cría «ilegítima» de la sociedad dominante y el movimiento social de oposición, de la ciencia y la tecnología, de lo humano y la máquina, del «primer» y «tercer» mundo, del macho/varón y la hembra/mujer, de hecho, de cada par binario. La cualidad híbrida de esta criatura se sitúa, en relación a cada extremo de estas posiciones binarias y a cada deseo de totalidad, escribe Haraway, igual que la «blasfemia» (1995, p.251)  se posiciona en relación al cuerpo de la religión. La blasfemia de Haraway es el cyborg, el cual reprocha, desafía, transforma y escandaliza. un «feminismo cyborg» que sea «más capaz»    &lt;br /&gt;
que los feminismos de tiempos anteriores, escribe, de «mantenerse en sintonía con posicionamientos históricos y políticos específicos y con parcialidades permanentes sin abandonar la búsqueda de vínculos poderosos». Gayatari Spivak en su ejemplo de «esencialismo estratégico» que aboga tanto a favor de la movilidad como de la consolidación de la identidad al mismo tiempo. Las diferencias, escribe Haraway, deberían verse como ejemplos de «especificidad elaborada» y como una oportunidad para «el cuidado afectuoso que las personas deberían mostrar para aprender cómo ver fielmente desde el punto de vista del otro» (1995, p. 327). &lt;br /&gt;
// Cyborg: dedicated issue in Hysteria mexican magazine &lt;br /&gt;
http://hysteria.mx/editorial-8/&lt;br /&gt;
El  presente número de Hysteria aborda las problemáticas del cyborg, figura  prestada de la ciencia ficción, del ámbito bélico y espacial, para  reflexionar sobre la reconstrucción del cuerpo. Sin  embargo, presentamos al lector una selección de propuestas desmarcadas  del imaginario imperialista que, en sus múltiples representaciones  falocéntricas, mitad robot mitad humano, dominan el imaginario cultural.  Procuramos elegir obras textuales y visuales que se alejan de aquel  proyecto hipermoderno y militarmente omniabarcante, tanto en el orden de  lo simbólico como en lo social. Viramos, entonces, hacia una noción de cyborg afín  a las políticas corporales. Porque sustituir la carne, los órganos, o  los huesos, por metal o mecanismos, no es el verdadero problema, como  tampoco expandir las capacidades corporales. El cyborg existe pero la  condición corporal continúa imponiéndose. De igual modo, la psique  predomina, con sus problemas atemporales, sus miedos, sus placeres y sus  deseos, etc. En todo caso, nos interesan las modificaciones a las que  se somete el sujeto cuando no son efectuadas desde y para el sistema de  dominación en el cual se halla inmerso, sino cuando estas  trasformaciones son diseñadas por él mismo, en pos de una  performatividad disidente.&lt;br /&gt;
Hysteria es una  revista de cultura y sexualidad dirigida a personas interesadas en  explorar las políticas de representación del cuerpo desde la perspectiva  del arte y la búsqueda del placer entendidos como espacios políticos.&lt;br /&gt;
// The Cyberpunk Project&lt;br /&gt;
“Cyborg” is a science-fictional shorting of “cybernetic  organism”. The idea is that, in the near future, we may have more and  more artificial body parts – arms, legs, hearts, eyes – and digital  computing and communication supplements. The logical conclusion is that  one might become a brain in a wholly artificial body. And the step after  that is to replace your meat brain by a computer brain.&lt;br /&gt;
// Cyborg soldiers and militarised masculinities &amp;gt; http://www.eurozine.com/articles/2010-05-20-masters-en.html&lt;br /&gt;
Cyborg Soldiers http://www.slate.com/articles/health_and_science/human_nature/2007/11/cyborg_soldiers.html&lt;br /&gt;
http://www.chisasibi.org/world-war-1-soldiers-equipment&lt;br /&gt;
Soldier’s Disease&lt;br /&gt;
http://wiki.addictiontreatmentmagazine.com/medical/mental-health/soldier-s_disease/&lt;br /&gt;
// CYBORG ++LINKS&lt;br /&gt;
http://cyborganthropology.com/Main_Page&lt;br /&gt;
http://escritorasfantastikas.blogspot.com.es/&lt;br /&gt;
http://entregrietas.wordpress.com/tag/cibertransitos/&lt;br /&gt;
http://www.macba.cat/ca/trobades-entre-especies-el-feminisme-darrere-els-ciborgs&lt;br /&gt;
http://www.medienkunstnetz.de/themes/cyborg_bodies/&lt;br /&gt;
http://cyberartsweb.org/cpace/theory/hoofd/index.html&lt;br /&gt;
http://project.cyberpunk.ru/&lt;br /&gt;
http://www.blog.lucysombra.org/category/cyborg/&lt;br /&gt;
// FuturismS&lt;br /&gt;
From: Janelle Monáe: A New Pioneer Of Afrofuturism    &lt;br /&gt;
http://thequietus.com/articles/04889-janelle-mon-e-the-archandroid-afrofuturism     &lt;br /&gt;
&lt;br /&gt;
    &amp;quot;I'm a cybergirl without a face a heart or a mind,&lt;br /&gt;
&lt;br /&gt;
(a product of the man, I'm a product of the man),&lt;br /&gt;
I'm a saviour without a race (without a face).&amp;quot;&lt;br /&gt;
Janelle Monáe on 'Violet Stars Happy Hunting', from her debut EP 'The Chase'&lt;br /&gt;
&lt;br /&gt;
      the means to battle an oppressive regime and liberate the 'have not's  of society. Consider that the word 'machine' is thought by some to be  derived from the Greek word for remedy.&lt;br /&gt;
&lt;br /&gt;
    &amp;quot;In the era of slavery, people of African descent were human enough to  live and love and have culture, but were nonhuman to the extent that  they were 'machines', labour for capitalism&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
    Others perceive Afrofuturism as in conflict to the idea of even being  human, which music critic Kodwo Eshun describes as a &amp;quot;treacherous  category&amp;quot; for the Afrofuturist. If you aren't human neither can you be  &amp;quot;subhuman&amp;quot; or &amp;quot;nonhuman&amp;quot;, common descriptions in civilised societies for  'the other' i.e the marginalized ethnic classes, the impoverished and  the homosexuals - the &amp;quot;semiotic ghosts&amp;quot;, as William Gibson saw it. It is  part of a rejection of &amp;quot;black humanist&amp;quot; culture in favour of a new  subjectivity which jettisons the traditional image of &amp;quot;black bodies in  pain&amp;quot; expressed in blues and soul. Thus, if you're &amp;quot;intergalactic  funkadelic&amp;quot; (as George Clinton liked to put it), no longer is 'the self'  defined reactively by the freedom struggle against white oppressors,  who are allowed a presence by inference and thus are free to  over-determine African-American culture. As one blogger and Berkeley  history graduate Arri Acornly interprets this: &amp;quot;Black women can explore  the physical expressions of her feminine form without being sexualised  and animalised. A black man can just be a man and not a black man.&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
From: http://fyeahafrofuturism.tumblr.com/&lt;br /&gt;
&lt;br /&gt;
    &amp;quot;Afrofuturism, for me, is about speculating on the potentiality of  what is known about technology and physics to create metaphors that  allow me to explore an African diasporic past and generate possible  narratives for the future…Afrofuturism is also a rumination on memories  to which I have no access. My investment in it as a production strategy  has run its course; Afrofuturism provides a way to investigate trauma  very explicitly. But we only reenact traumas, don’t we? We don’t reenact  prom night, or our favorite birthday party. This is a problem—it  doesn’t seem to fix things; it amplifies them. There’s gotta be  something else, the after-the-trauma.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Cauleen Smith (Cauleen is a player in the movement of Afrofuturism,  an emergent literary and cultural aesthetic that combines elements of  science fiction, historical fiction, fantasy, Afrocentricity, and magic  realism with non-Western cosmologies in order to critique not only the  present-day dilemmas of people of color, but also to revise,  interrogate, and re-examine the historical events of the past - wiikipedia)&lt;br /&gt;
&lt;br /&gt;
    &amp;quot;Black existence and science fiction are one in the same.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Kodwo Eshun, “Further Considerations of Afrofuturism,”&lt;br /&gt;
// Lydia Lunch quotes  &lt;br /&gt;
... about change of self paradigmas&lt;br /&gt;
“I had to de-program myself. From myself. Had to reinvent rituals of purification. So full of the vagrant pollutions of others. It was time to detox. Not only from alcohol, sex, and drugs, but from needy leeches who looked to swab me with their sores. Detox from my own needy lechery. Had to locate the center wound and cauterize. Undo the original sin, the origin of my sickness...Had to learn to replace Them, It, Want, Hurt, Anger, Sorrow, Loss, with Power, Healing, Wisdom, Fulfillment, Satisfaction.”&lt;br /&gt;
― Lydia Lunch, Paradoxia: A Predator's Diary &lt;br /&gt;
// Walter Benjamin&lt;br /&gt;
The  art of the critic in a nutshell: to coin slogans without betraying  ideas. The slogans of an inadequate criticism peddle ideas to fashion.&lt;br /&gt;
Read more at http://www.brainyquote.com/quotes/authors/w/walter_benjamin.html#FgQ5rpl4cKTBGgFt.99&lt;br /&gt;
// Tecnochamanismo &amp;amp; Ecotécnia: other conceptual aproaches to tech+bodypolitics&lt;br /&gt;
http://tecnoxamanismo.metareciclagem.org/index.php?title=Espanhol&lt;br /&gt;
http://tecnoxamanismo.hotglue.me/&lt;br /&gt;
Las Ecotecnias son instrumentos desarrollados por el  hombre a través del tiempo, se caracterizan por aprovechar  eficientemente los recursos naturales y usar materiales de bajo impacto  para dar paso a la elaboración de productos y servicios (Wilkipedia,  2009)&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
	<entry>
		<id>https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=22</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://alexandria.anarchaserver.org/index.php?title=Main_Page&amp;diff=22"/>
		<updated>2014-09-26T18:25:09Z</updated>

		<summary type="html">&lt;p&gt;Thf: /* Documentation TransHackFeminist 2014 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
[[File:8 THF wangechi-mutu-uterine-catarrh.png]]&lt;br /&gt;
&lt;br /&gt;
== Anarcha Server ==&lt;br /&gt;
&lt;br /&gt;
* [[Who was Anarcha?]]&lt;br /&gt;
* [[Anarcha feminesto: Why a feminist server?]]&lt;br /&gt;
* [[Policy: Aims, working methodologies, sustainability]]&lt;br /&gt;
* [[Future is now: Milestones]]&lt;br /&gt;
&lt;br /&gt;
== Documentation TransHackFeminist 2014  ==&lt;br /&gt;
&lt;br /&gt;
* [[Servidor feminista/Feminist Server]]&lt;br /&gt;
* [[Anarchagland]]&lt;br /&gt;
* [[Seguridad digital/Digital Security]]&lt;br /&gt;
* [[Taller de teatro de la emancipación / Theatre of the Emancipation Workshop]]&lt;br /&gt;
* [[Taller de Recreación feminista, hackeando vídeos de internet / Feminist Recreation Workshop, hacking videos from the Internet]]&lt;br /&gt;
* [[The Fellatio Modification Project]]&lt;br /&gt;
* [[Satellite Fishing/Pescando satélites]]&lt;br /&gt;
* [[TransHackFeminist/Que significa?/What it means?]]&lt;br /&gt;
* [[R_R/R Radio Ramona and Ruelles]]&lt;br /&gt;
* [[Que es genitalismo?/What Is Genitalism?]]&lt;br /&gt;
* [[Cyborg Romanticism]]&lt;br /&gt;
* [[HerStory]]&lt;br /&gt;
* [[Armas de Destrucción de Misa: diseño en Gimp y HotGlue / Mass Destruction Weapons: Gimp and HotGlue Workshop]]&lt;br /&gt;
* [[Tacticas Feministas en la red/Feminist Tactis in the Net]]&lt;br /&gt;
* [[UpStage, plataforma de codigo abierto para cyberperformaces/Upstage, open source platform for cyberperformance]]&lt;br /&gt;
* [[Cómo jugar en tu ordenador y no cargarte el sistema / How to play in your computer without knocking off the system]]&lt;br /&gt;
* [[Gynepunk BioLab + Del EM, sistema de extracción menstrual / Menstrual extraction systemy]]&lt;br /&gt;
* [[Open Street Map Mapping Party]]&lt;br /&gt;
* [[Bibliotecas publicas digitales/Book Scan]]&lt;br /&gt;
* [[Hacking Gender Construction]]&lt;br /&gt;
* [[Primero Auxilios en Caso aborto y Derrame / First Aid in case of abortion]]&lt;br /&gt;
* [[Experimental Fanzinoteka/ Experimental fanzinotheque]]&lt;br /&gt;
* [[Hacking Acadamia]]&lt;br /&gt;
* [[Los tullidxs están buenos, son transmaricabolleros y follan/ Crips are hot, queer and they fuck]]&lt;br /&gt;
* [[Cafes de la muerte/Death Cafes]] &lt;br /&gt;
* [[Pornotrash]]    &lt;br /&gt;
&lt;br /&gt;
* [[Dossier Memoria THF/Memory report THF]]&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [//meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]&lt;br /&gt;
* [//www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]&lt;br /&gt;
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>Thf</name></author>
	</entry>
</feed>