Actually, I was quite glad to see you post the files, until I discovered they were for openssl, and not openssh.
I too have been hoping to have openssh 3.7.1p1-2 show up in a fink selfupdate-cvs, as I noted the web site showed this version in unstable several days ago. But it appears that the problems with SourceForge are so severe that Fink updates are now a waste of time, as I have not received any new versions of anything for several days.
SourceForge keeps saying that they have a plan to improve the situation, but it never seems to happen. I hope Max is working on a way to divorce Fink from SourceForge, because it has become pretty much impossible for an anonymous user to get any new .info files with a fink selfupdate-cvs. I used to be comfortable knowing that Fink would provide me with timely updates to critical software such as openssh. I know the developers have done their bit by updating the package, but it is a wasted effort if the users cannot access them.
Don't take this the wrong way - I am very appreciative of the efforts that have gone into Fink. I am just frustrated to see it being dragged down by SourceForge's problems.
Kevin Horton
At 15:52 -0400 20/9/03, Alexander Hansen wrote:
Oops--accidentally posted to the list there.
On Saturday, September 20, 2003, at 03:42 PM, Alexander Hansen wrote:
If you haven't gotten them yet, I've attached a tarball (to keep from introducing stray newlines).
<openssl.tar.gz>
-- Alexander K. Hansen Levitated Dipole Experiment http://www.psfc.mit.edu/LDX
On Saturday, September 20, 2003, at 02:54 PM, William Scott wrote:
Hi Folks:
A few days ago openssh Version 3.7.1p1-2 was apparently put into fink unstable.
I cannot find the info and patch files for this. I just cvs selfupdated (again) 2 minutes ago and the latest version I can find in /sw/fink/dists/unstable/crypto/finkinfo is 3.6.1
I therefore edited that file and put in the newer version. Everything compiled and installed, and ssh works, but sshd won't let me log in remotely. I followed the directions in the info file and that all seemed to have gone smoothly.
Manually replacing the new sshd with my older version cures this problem, indicating it isn't the configuration files it is reading, but the binary itself, that is problematic.
Although it cures the problem, I assume I reintroduced the security hole, so it isn't really a cure.
At this point I can't help but think I am trying to resolve a problem Max Horn already solved, but unfortunately don't have access to the up to date openssh info and patch files
If someone has these could you please email them to me?
Thanks.
Bill
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
