Vhosts... and key negotiation screwed
Secure chat and conferencing protocol
Brought to you by:
priikone
From: damm <da...@bo...> - 2002-05-28 19:15:47
|
> Anyone notice a key negotiation problems? > > Here's my problem, shell.bourg.net 207.229.76.2 has a interface > 207.229.76.120 for livid.de, i do > silc -h livid.de > > 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. > > My problem is more that it should have went to .120 instead of .2, but i > was wondering the status of the private keys. > > That and i modified the hmac and cipher on channel bsd, > > and no one can listen to anyone, i changed it to, > > hmad-md5-96 > > and the cipher to, > > cast-192-cbc > > I cannot figure out how to convert the channel to private keys via /key > channel bsd change private > > doesn't do/say anything. > > Any thoughts? > > Thanks > |