search for: riverstonenet

...er, MAC and compression for the other direction client-to-server of the same connection. Is this supported today in OpenSSH, and if not, are there plans to support it in any future releases of the code? If so, in which release is it planned? Thanks ------ Behnam Behzadi 408-878-6551 http://www.riverstonenet.com

I havent had the time to look into this further, and since i'm not a much of a C progammer, i'm afraid i might never figure it out so i thought i'd report it here. i'm running icecast 1.3.11 and feeding it with iceS 0.2.2. i've got 7 streams running, each running a different playlist out of my collection in random order. one of the streams runs for a few hours and then

Hi, According to IETF draft draft-ietf-secsh-transport-14.txt, different ciphers(encryption), MAC and compression can be used for one direction say server-to-client and a completely different cipher, MAC and compression for the other direction client-to-server of the same connection. Is this supported today in OpenSSH, and if not, are there plans to support it in any future releases of the

Hi, We found that the OpenSSH server code sends it version string as "SSH-1.5_OpenSSH_3.5" to the client during the intial phases of connection establishment. Futher more some clients like telnet client displays this version string on error. Like for example if we typed "Telnet host <> port 22" on a solaris workstation, where the host is a machine which is running