search for: rhardi

Three possibly related bugs to report. N.B. The test machines in question are in peak form (with the exception of different kernel versions) and were working 100% under the old ssh 1.2.x. The two clients we tested from are machines running 2.2.13 & 2.2.14preX Linux kernels. The server where the problems appeared is running 2.2.12. 1. sshd dies periodically. The crash occurred just after a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just released 1.2pre14 at: http://violet.ibs.com.au/openssh/ Changes: Attempt to make <enter> close gnome-ssh-askpass. This works OK when gnome-ssh-askpass is run from the commandline, but doesn't work when it is run from ssh-add. Further investigation is required. Lots of portability fixes. The ssh client now appears to run

A bug has found its way into Openssh-1.2pre15. It has forced us to downgrade to pre14. Our test hosts are connected with regular Ethernet and by an internal VPN. With that in mind, any given host has two IP addresses. Starting with pre15 we get the fatal error message below every time we connect to the EXTERNAL ip address (eth0). For some reason, we continue to be able to connect to the INTERNAL

A little over a week ago I posted asking about setting up a linux box between an existing router and a switch in order to provide firewall service to a subnet of machines. I was curious what experience others had with this type of setup in terms of machines, configurations, and the appropriateness of using linux in this manner. There were basically three issues discussed in replies: hardware

Hi Are there any known security holes or necessary precautions in using port forwarding with ipportfw? I'm planning on forwarding ports from an outer firewall/router (connected to the Internet) to a host in the DMZ, then on from the DMZ host to the inner firewall, and finally from the inner firewall to some host on the inside. Thanks, Jens jph@strengur.is From mail@mail.redhat.com Wed