Secure User Identification - Revision history

Vollstrecker: Corrected Spelling of Deutsch in language selection

2008-08-04T14:25:54Z

Corrected Spelling of Deutsch in language selection

Vollstrecker: Fixed Typos and Removed Version Tag

2008-06-29T09:22:50Z

Fixed Typos and Removed Version Tag

Vollstrecker: Adjusted Links

2008-01-22T11:07:30Z

Adjusted Links

Vollstrecker: Adjusted Links, Added Version-Tag

2008-01-22T09:00:29Z

Adjusted Links, Added Version-Tag

Ihmselbst: added -de link

2006-02-25T07:30:03Z

added -de link

209.210.229.214 at 13:47, 7 September 2005

2005-09-07T13:47:05Z

JohnGH: =What is Secure User Identification (SUI) ?=

2005-06-11T00:00:50Z

=What is Secure User Identification (SUI) ?=

JohnGH: =What is Secure User Identification (SUI) ?=

2005-06-11T00:00:32Z

=What is Secure User Identification (SUI) ?=

Jacobo221 at 23:55, 16 October 2004

2004-10-16T23:55:49Z

Jacobo221: beginning the job...

2004-10-16T23:04:23Z

beginning the job...

← Older revision		Revision as of 14:25, 4 August 2008
Line 1:		Line 1:
−	<center>'''English''' \| [[Secure_User_Identification-de\|~~German~~]]</center>	+	<center>
		+	'''English''' \|
		+	[[Secure_User_Identification-de\|Deutsch]]
		+	</center>

	== What is Secure User Identification (SUI) ? ==		== What is Secure User Identification (SUI) ? ==

@@ Line 14: / Line 14: @@
 == First meeting ==
-When [[aMule]] connects to a client supporting SUI, it expects this client to send it's public key (it's user hash) along with a random number, while [[aMule]] will do right the same. If the public key it gets is unknown, it will stored it in ''clients.met'' (only the public key, not the random number) so that it will be possible to identify that [[client]] next time it meets it.
+When [[aMule]] connects to a client supporting SUI, it expects this client to send it's public key (it's user hash) along with a random number, while [[aMule]] will do right the same. If the public key it gets is unknown, it will store it in ''clients.met'' (only the public key, not the random number) so that it will be possible to identify that [[client]] next time it meets it.
 == Identificating ==
-When a [[client]] wants to identify in another [[client]], it will send to this latter [[client]] a [[digital signature]] created from it's own private key, the public key of the other [[client]] and the random value the other [[client]] sent.
+When a [[client]] wants to identify to another [[client]], it will send to this latter [[client]] a [[digital signature]] created from it's own private key, the public key of the other [[client]] and the random value the other [[client]] sent.
 The other [[client]] will do the same.
@@ Line 25: / Line 25: @@
 Of course, your [[client]] will do exactly the same with the [[digital signature]] it gets from the remote [[client]].

@@ Line 3: / Line 3: @@
 == What is Secure User Identification (SUI) ? ==
 [[Client|Clients]] in the network are identified by a unique value called [[Userhash|user hash]]. This user hash is stored in the ''preferences.dat'' file and is used to grant earned [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|credits]] with other users.
-[[AMule Project FAQ:About|aMule]] (like [[eMule]]) can use an asymmetric encryption to avoid exploiting or manipulating other user hash values. The method uses a private and a public key to ensure a correct and unique identification on other clients.
+[[aMule]] (like [[eMule]]) can use an asymmetric encryption to avoid exploiting or manipulating other user hash values. The method uses a private and a public key to ensure a correct and unique identification on other clients.
-Secure User Identification can be turned on in Preferences -> Connection (since [[AMule Project FAQ:About|aMule]] 2.x, version 2.0.3 has it under Preferences -> Security). It is recommended to use it.
+Secure User Identification can be turned on in Preferences -> Connection (since [[aMule]] 2.x, version 2.0.3 has it under Preferences -> Security). It is recommended to use it.
 == The identification process ==
 The following describes how two [[client]]s supporting SUI identify each other. If the identification fails, the [[client]] which detects the failure should ban the other [[client]].
-== First [[AMule Project FAQ:About|aMule]] start ==
+== First [[aMule]] start ==
-When you start [[AMule Project FAQ:About|aMule]] for the first time, it will create a 384-bit [http://en.wikipedia.org/wiki/RSA RSA] private key (which will be stored in ''cryptkey.dat''). This file should be kept forever, since losing it will make you lose all your credits.
+When you start [[aMule]] for the first time, it will create a 384-bit [http://en.wikipedia.org/wiki/RSA RSA] private key (which will be stored in ''cryptkey.dat''). This file should be kept forever, since losing it will make you lose all your credits.
 == First meeting ==
-When [[AMule Project FAQ:About|aMule]] connects to a client supporting SUI, it expects this client to send it's public key (it's user hash) along with a random number, while [[AMule Project FAQ:About|aMule]] will do right the same. If the public key it gets is unknown, it will stored it in ''clients.met'' (only the public key, not the random number) so that it will be possible to identify that [[client]] next time it meets it.
+When [[aMule]] connects to a client supporting SUI, it expects this client to send it's public key (it's user hash) along with a random number, while [[aMule]] will do right the same. If the public key it gets is unknown, it will stored it in ''clients.met'' (only the public key, not the random number) so that it will be possible to identify that [[client]] next time it meets it.
 == Identificating ==
@@ Line 28: / Line 28: @@
 == Version ==
 Created by "Unknown User" on 03.05.04 at 18:10<br>
-Updated by Vollstrecker on 22.01.08 | at 10:00
+Updated by Vollstrecker on 22.01.08 | at 12:07

@@ Line 2: / Line 2: @@
 == What is Secure User Identification (SUI) ? ==
 [[Client|Clients]] in the network are identified by a unique value called [[Userhash|user hash]]. This user hash is stored in the ''preferences.dat'' file and is used to grant earned [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|credits]] with other users.
-[[aMule]] (like [[eMule]]) can use an asymmetric encryption to avoid exploiting or manipulating other user hash values. The method uses a private and a public key to ensure a correct and unique identification on other clients.
+[[AMule Project FAQ:About|aMule]] (like [[eMule]]) can use an asymmetric encryption to avoid exploiting or manipulating other user hash values. The method uses a private and a public key to ensure a correct and unique identification on other clients.
-Secure User Identification can be turned on in Preferences -> Connection (since [[aMule]] 2.x, version 2.0.3 has it under Preferences -> Security). It is recommended to use it.
+Secure User Identification can be turned on in Preferences -> Connection (since [[AMule Project FAQ:About|aMule]] 2.x, version 2.0.3 has it under Preferences -> Security). It is recommended to use it.
 == The identification process ==
 The following describes how two [[client]]s supporting SUI identify each other. If the identification fails, the [[client]] which detects the failure should ban the other [[client]].
-== First [[aMule]] start ==
+== First [[AMule Project FAQ:About|aMule]] start ==
+When you start [[AMule Project FAQ:About|aMule]] for the first time, it will create a 384-bit [http://en.wikipedia.org/wiki/RSA RSA] private key (which will be stored in ''cryptkey.dat''). This file should be kept forever, since losing it will make you lose all your credits.
 When you start [[aMule]] for the first time, it will create a 384-bit [http://en.wikipedia.org/wiki/RSA RSA] private key (which will be stored in ''cryptkey.dat''). This file should be kept forever, since losing it will make you lose all your credits.
 == First meeting ==
+When [[AMule Project FAQ:About|aMule]] connects to a client supporting SUI, it expects this client to send it's public key (it's user hash) along with a random number, while [[AMule Project FAQ:About|aMule]] will do right the same. If the public key it gets is unknown, it will stored it in ''clients.met'' (only the public key, not the random number) so that it will be possible to identify that [[client]] next time it meets it.
 When [[aMule]] connects to a client supporting SUI, it expects this client to send it's public key (it's user hash) along with a random number, while [[aMule]] will do right the same. If the public key it gets is unknown, it will stored it in ''clients.met'' (only the public key, not the random number) so that it will be possible to identify that [[client]] next time it meets it.
 == Identificating ==
 When a [[client]] wants to identify in another [[client]], it will send to this latter [[client]] a [[digital signature]] created from it's own private key, the public key of the other [[client]] and the random value the other [[client]] sent.
@@ Line 27: / Line 22: @@
 == Validating an identification ==
 When the remote [[client]] get's this signature, it will check if it is created from the your public key and the random value it sent, and then check if it suits it's own private key. If both checks succeed, your [[client]] will be successfully identified on that [[client]].
 Of course, your [[client]] will do exactly the same with the [[digital signature]] it gets from the remote [[client]].

@@ Line 1: / Line 1: @@
 == What is Secure User Identification (SUI) ? ==
@@ Line 12: / Line 14: @@
 == First [[aMule]] start ==
-When you start [[aMule]] for the first time, it will create a 384-bit [http://en.wikipedia.org/wiki/RSA RSA] private key (which will be stored in ''cryptkey.dat''). This file should be kept forever, since loosing it will make you loose all your credits.
+When you start [[aMule]] for the first time, it will create a 384-bit [http://en.wikipedia.org/wiki/RSA RSA] private key (which will be stored in ''cryptkey.dat''). This file should be kept forever, since losing it will make you lose all your credits.
 == First meeting ==
@@ Line 28: / Line 30: @@
 When the remote [[client]] get's this signature, it will check if it is created from the your public key and the random value it sent, and then check if it suits it's own private key. If both checks succeed, your [[client]] will be successfully identified on that [[client]].
-Of course, your [[client]] will do exactly the same with the [[digital signature]] it gets fromthe remote [[client]].
+Of course, your [[client]] will do exactly the same with the [[digital signature]] it gets from the remote [[client]].

← Older revision		Revision as of 23:55, 16 October 2004
Line 6:		Line 6:
	Secure User Identification can be turned on in Preferences -> Connection (since [[aMule]] 2.x). It is recommended to use it.		Secure User Identification can be turned on in Preferences -> Connection (since [[aMule]] 2.x). It is recommended to use it.

−	The identification process ~~goes as follows~~:	+	== The identification process ==
		+
		+	The following describes how two [[client]]s supporting SUI identify each other. If the identification fails, the [[client]] which detects the failure should ban the other [[client]].
		+
		+	== First [[aMule]] start ==
		+
		+	When you start [[aMule]] for the first time, it will create a 384-bit [http://en.wikipedia.org/wiki/RSA RSA] private key (which will be stored in ''cryptkey.dat''). This file should be kept forever, since loosing it will make you loose all your credits.
		+
		+	== First meeting ==
		+
		+	When [[aMule]] connects to a client supporting SUI, it expects this client to send it's public key (it's user hash) along with a random number, while [[aMule]] will do right the same. If the public key it gets is unknown, it will stored it in ''clients.met'' (only the public key, not the random number) so that it will be possible to identify that [[client]] next time it meets it.
		+
		+	== Identificating ==
		+
		+	When a [[client]] wants to identify in another [[client]], it will send to this latter [[client]] a [[digital signature]] created from it's own private key, the public key of the other [[client]] and the random value the other [[client]] sent.
		+
		+	The other [[client]] will do the same.
		+
		+	== Validating an identification ==
		+
		+	When the remote [[client]] get's this signature, it will check if it is created from the your public key and the random value it sent, and then check if it suits it's own private key. If both checks succeed, your [[client]] will be successfully identified on that [[client]].
		+
		+	Of course, your [[client]] will do exactly the same with the [[digital signature]] it gets fromthe remote [[client]].

@@ Line 2: / Line 2: @@
 [[Client|Clients]] in the network are identified by a unique value called user hash. This user hash is stored in the ''preferences.dat'' file and is used to grant earned [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|credits]] with other users.
-[[aMule]] (like [[eMule]]) can use an asymmetric encryption to avoid exploiting or manipulating other user hash values. The method uses a private and a public key to secure the user hash and to ensure a proper identification on other clients.
+[[aMule]] (like [[eMule]]) can use an asymmetric encryption to avoid exploiting or manipulating other user hash values. The method uses a private and a public key to ensure a correct and unique identification on other clients.
 Secure User Identification can be turned on in Preferences -> Connection (since [[aMule]] 2.x). It is recommended to use it.
-Other sources: http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=135
+The identification process goes as follows:
-−
-(The above source's information will be soon summarized here)