search for: membl

Please read the following notes regarding your project at freshmeat.net: - olly at survex.com has requested ownership of the freshmeat record for your project. Do you approve this change? If you are not sure what this means, please see http://freshmeat.net/faq/view/46/. Sincerely, Ray Shaw <news-admins at freshmeat.net> --- Headers Follow --- >From noreply at freshmeat.net Mon Sep

...ple <ftp://ftp.plig.org/pub/OpenBSD/OpenSSH/portable/snapshot/> stops in 2005-03-07 while the same directory on the master site has recent files. I don't know whether this outdatedness applies only to the Portable OpenSSH snapshots or to the whole OpenBSD tree. -- Ed Avis <ed at membled.com>

...le suggested fsh as a way of speeding up a build system which sshes to different hosts to run jobs in parallel. fsh is very handy but it works by keeping open a *single* connection. It won't work if you want to execute more than one command in parallel on the same host. -- Ed Avis <ed at membled.com>

...t it looks like at the moment SA there is having almost as many troubles as that filtering the list itself. It would be possible to write some new SA rules to catch the 'suspicious message' crap, and then send them to either the list owner or the maintainer of Gmane. -- Ed Avis <ed at membled.com>

Below is a patch that adds the ability to have a none cipher and mac for protocol version 2. By default, sshd will not allow these to be used; an admin will have to explicitly allow them in the Ciphers and MACs section of sshd_config. Additionally, the client will not use these unless explicitly instructed to by the user. The actual name of the cipher is 'none2', to distinguish it

Hi there Is it possible to configure ssh so that a session can continue/recover after a change of IP? I have a number of static IP dialup accounts and there is no problem using these because when my dialup connection timesout and later reconnects, it gets the same IP and so any existing ssh sessions are unaffected. However, these accounts with static IP's are metered (i.e. expensive ;-).

Is it possible to use encryption only for authenticate and then switch to no encryption? I've looked at the code for OpenSSH 3.5p1, cipher.c, and it looks like the answer is no, at least for protocol 1. However, I cannot tell if that is a deliberate design limitation of the implementation or if it is inherent in ssh protocol 2. My dilemma is a customer who wants to use their network IDS