Re: Fw: SILC client connection issue

: I had similar problems with silc-toolkit 1.1.9.
: 
: I would suggest to look at the version of the private key you imported.
: 
: silcpk.c:silc_pkcs_silc_export_private_key(..)
: 
: will always save a private key in with version SILC_PRIVATE_KEY_VERSION_1,
: but
: 
: silcpk.c:silc_pkcs_silc_export_public_key(...)
: 
: will include an identifier with the actual version.
: 
: 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.
: 
This happens if you create the keypair without using the utility function 
silc_create_key_pair and specify the version to the identifier.  If I 
remember correctly I left this "bug" in on purpose because I wanted the 
software support for the version 2 public keys and private keys to 
populate before the software actually starts to create version 2 keys, so 
as to avoid interoperability problems when the switch is made, since none 
of the older versions supported versioning.

I think now would be a fine time to enable the version 2 keys by default.  
Anyone who is still using version of SILC that doesn't support versioned 
keys is just going to have to upgrade.

	Pekka
________________________________________________________________________
 Pekka Riikonen                                 priikone at silcnet.org
 Secure Internet Live Conferencing (SILC)       http://silcnet.org/
_______________________________________________________________________
Info:    https://lists.silcnet.org/mailman/listinfo/silc-announce
Archive: https://lists.silcnet.org/pipermail/silc-announce
FAQ:     http://silcnet.org/support/faq/