Re: editing "new" known_hosts files

LeVA wrote: I have reinstalled a server of mine, and now I need to remove it's old pubkey from my $HOME/.ssh/known_hosts, but it is in the "new" format, so no hostnames which may indicate which pubkey belongs to which host. In addition to what Steve wrote: OpenSSH specifies the conflicting li

Re: Idea to secure ssh [was: howto block ssh brute-force]

Neal Murphy wrote: The point is to reduce brute-forace attacks to the point of nearly total ineffectiveness. I use OpenSSH public/private key authentication to achieve this. Based on needs one could also use two factor authentication (e.g. one time password tokens) or even a combination of

Re: security.debian.org mirrors?

Fox wrote: > Why would you need a *full* mirror ? setting up apt-proxy on one of your > servers and using it as a security repository for the other servers you're > maintaining wouldn't do it ? Yes a good idea and it can save your own bandwidth too ;) I am using http-replicator [1] for both .deb d

Re: net unavailable

Hi Markus, i had similar issues with a Dlink 4 port NIC running Debian 3.0 and the sundance driver that was included with 2.4.18 (stability problems). I compiled my own sundance.o (newer version from the web) for my kernel, which solved the problems. I installed a second firewall last week (sa

custom sec updates, was Bad press related to (missing) Debian security

Marek Olejniczak wrote: I must use it. Sarge is working on a ISP production servers. I work for a medium-sized company and moved nearly all our application hosting server from wind0ze and SuSE to Debian. Debian is our choice for production servers. I'm working for many ISP providers. And