Re: Vhosts... and key negotiation screwed
Secure chat and conferencing protocol
Brought to you by:
priikone
From: Pekka R. <pri...@ik...> - 2002-05-29 15:18:48
|
: > and then do /key msg ax negotiate : > : > problem is it starts listening on 207.229.76.2 instead of .120, which in : > any sense of anyone's mind would scream ALARM why am i connecting to .2 : > instead of .120? : > : > [ax(tes...@80...)] send this too to them that : > i did : > a `/key msg damm negotiate 207.229.76.2 45430' and it resulted in : > an : > error sent to stdout. [<timestamp>] [Error] Cant connect to remote : > host: Invalid argument : > : > that's what ax got... when he tried to connect. Aparently it didnt even : > try and connect. : > If this is what you did then it seems you're not using the KEY correctly. The KEY's interface is bad, yes, but still it should work. Please see the FAQ for how to use the /KEY command to negotiate keys. http://silcnet.org/?page=faq#f3_40 Pekka ________________________________________________________________________ Pekka Riikonen priikone at silcnet.org Secure Internet Live Conferencing (SILC) http://silcnet.org/ |