Re: Fw: SILC client connection issue
"Hansa" <[email protected]> Wed, 1 Apr 2009 10:25:25 +0530
| Newsgroups | gmane.network.silc.devel |
|---|---|
| Message-ID | <005201c9b286$12aab930$ab01a8c0@hansa> |
This is a multi-part message in MIME format. --===============1285706317== Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01C9B2B4.2B8EB540" This is a multi-part message in MIME format. ------=_NextPart_000_004F_01C9B2B4.2B8EB540 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Pekka, Nice to hear from you. I have given identifier string in = silc_create_key_pair function and given tried with V=3D1 and V=3D2 both. = But it still says me Error during key exchange with silc.silcnet.org: = Incorrect signature. How to resolve this and get connected to SILC server? Thanks & Regards Hansa ----- Original Message -----=20 From: "Pekka Riikonen" <[email protected]> To: "Ivo Clarysse" <[email protected]> Cc: "Hansa" <[email protected]>; <silc-devel-cR8azDVoa3JZ/hxrHI3Fm9i2O/[email protected]> Sent: Tuesday, March 31, 2009 11:12 PM Subject: Re: Fw: SILC client connection issue >=20 > : I had similar problems with silc-toolkit 1.1.9. > :=20 > : I would suggest to look at the version of the private key you = imported. > :=20 > : silcpk.c:silc_pkcs_silc_export_private_key(..) > :=20 > : will always save a private key in with version = SILC_PRIVATE_KEY_VERSION_1, > : but > :=20 > : silcpk.c:silc_pkcs_silc_export_public_key(...) > :=20 > : will include an identifier with the actual version. > :=20 > : So, when you create a version 2 key pair, and save those keys using = the > : above mentioned silcpk.c functions, you end up with a private key in = version > : 1, and a public key in version 2. > :=20 > This happens if you create the keypair without using the utility = function=20 > silc_create_key_pair and specify the version to the identifier. If I=20 > remember correctly I left this "bug" in on purpose because I wanted = the=20 > software support for the version 2 public keys and private keys to=20 > populate before the software actually starts to create version 2 keys, = so=20 > as to avoid interoperability problems when the switch is made, since = none=20 > of the older versions supported versioning. >=20 > I think now would be a fine time to enable the version 2 keys by = default. =20 > Anyone who is still using version of SILC that doesn't support = versioned=20 > keys is just going to have to upgrade. >=20 > Pekka > = ________________________________________________________________________ > Pekka Riikonen priikone at silcnet.org > Secure Internet Live Conferencing (SILC) http://silcnet.org/ >=20 > ------=_NextPart_000_004F_01C9B2B4.2B8EB540 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.2853" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV><FONT face=3DArial size=3D2>Hi Pekka,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Nice to hear from you. I = have given identifier=20 string in silc_create_key_pair function and given tried with V=3D1 and = V=3D2 both.=20 But it still says me <FONT color=3D#800080>Error during key exchange = with=20 silc.silcnet.org: Incorrect signature.</FONT></FONT></DIV> <DIV><FONT face=3DArial color=3D#800080 size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>How to resolve this and get connected = to SILC=20 server?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks & Regards</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Hansa</FONT></DIV> <DIV><FONT face=3DArial size=3D2>----- Original Message ----- </FONT> <DIV><FONT face=3DArial size=3D2>From: "Pekka Riikonen" <</FONT><A=20 href=3D"mailto:[email protected]"><FONT face=3DArial=20 size=3D2>[email protected]</FONT></A><FONT face=3DArial = size=3D2>></FONT></DIV> <DIV><FONT face=3DArial size=3D2>To: "Ivo Clarysse" <</FONT><A=20 href=3D"mailto:[email protected]"><FONT face=3DArial=20 size=3D2>[email protected]</FONT></A><FONT face=3DArial=20 size=3D2>></FONT></DIV> <DIV><FONT face=3DArial size=3D2>Cc: "Hansa" <</FONT><A=20 href=3D"mailto:[email protected]"><FONT face=3DArial=20 size=3D2>[email protected]</FONT></A><FONT face=3DArial size=3D2>>; = <</FONT><A=20 href=3D"mailto:silc-devel-cR8azDVoa3JZ/hxrHI3Fm9i2O/[email protected]"><FONT face=3DArial=20 size=3D2>silc-devel-cR8azDVoa3JZ/hxrHI3Fm9i2O/[email protected]</FONT></A><FONT face=3DArial=20 size=3D2>></FONT></DIV> <DIV><FONT face=3DArial size=3D2>Sent: Tuesday, March 31, 2009 11:12 = PM</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Subject: Re: Fw: SILC client connection = issue</FONT></DIV></DIV> <DIV><FONT face=3DArial><BR><FONT size=3D2></FONT></FONT></DIV><FONT = face=3DArial=20 size=3D2>> <BR>> : I had similar problems with silc-toolkit = 1.1.9.<BR>> :=20 <BR>> : I would suggest to look at the version of the private key you = imported.<BR>> : <BR>> :=20 silcpk.c:silc_pkcs_silc_export_private_key(..)<BR>> : <BR>> : will = always=20 save a private key in with version SILC_PRIVATE_KEY_VERSION_1,<BR>> : = but<BR>> : <BR>> : = silcpk.c:silc_pkcs_silc_export_public_key(...)<BR>>=20 : <BR>> : will include an identifier with the actual version.<BR>> = :=20 <BR>> : So, when you create a version 2 key pair, and save those keys = using=20 the<BR>> : above mentioned silcpk.c functions, you end up with a = private key=20 in version<BR>> : 1, and a public key in version 2.<BR>> : = <BR>> This=20 happens if you create the keypair without using the utility function = <BR>>=20 silc_create_key_pair and specify the version to the identifier. If = I=20 <BR>> remember correctly I left this "bug" in on purpose because I = wanted the=20 <BR>> software support for the version 2 public keys and private keys = to=20 <BR>> populate before the software actually starts to create version = 2 keys,=20 so <BR>> as to avoid interoperability problems when the switch is = made, since=20 none <BR>> of the older versions supported versioning.<BR>> = <BR>> I=20 think now would be a fine time to enable the version 2 keys by = default. =20 <BR>> Anyone who is still using version of SILC that doesn't support=20 versioned <BR>> keys is just going to have to upgrade.<BR>> = <BR>>=20 Pekka<BR>>=20 ________________________________________________________________________<= BR>> Pekka=20 Riikonen  = ; = =20 priikone at silcnet.org<BR>> Secure Internet Live Conferencing=20 (SILC) </FONT><A=20 href=3D"http://silcnet.org/"><FONT face=3DArial=20 size=3D2>http://silcnet.org/</FONT></A><BR><FONT face=3DArial = size=3D2>>=20 <BR>></FONT></BODY></HTML> ------=_NextPart_000_004F_01C9B2B4.2B8EB540-- --===============1285706317== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________________________________ Info: https://lists.silcnet.org/mailman/listinfo/silc-announce Archive: https://lists.silcnet.org/pipermail/silc-announce FAQ: http://silcnet.org/support/faq/ --===============1285706317==--