Date: Thu, 3 Jun 1999 14:27:23 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Unknow User <kernel@tdnet.com.br>, Matthew Hunt <mph@astro.caltech.edu> Cc: freebsd-security@FreeBSD.ORG Subject: Re: SSH2 (in FreeBSD-Questions) Message-ID: <v04011701b37c74eab67f@[128.113.24.47]> In-Reply-To: <375690E3.4BC9BB94@tdnet.com.br> References: <37568B58.C48DCEA2@tdnet.com.br> <19990603102427.D58665@wopr.caltech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:27 PM +0000 6/3/99, Unknow User wrote: > No, i never use ports (Due to security problem)! > i always get the source! > > Any tips? Someone went to the time and trouble to fix all freebsd-related issues in ssh2, and you're just going to ignore that? Not only are you going to ignore that work, you're then going to complain about how the generally-available source does not happen to have freebsd-specific support in it? I'm not sure what your security hangup is with the ports collection, but the first tip I'd have is that you not complain after you have explicitly ignored work which people had already done to make your life easier. Even if you don't trust ports due to some security concern, there is nothing magic about what ports do. The second tip would be to look at the ssh2 information in ports, and do all steps yourself. You can ftp the files yourself, you can get the ports-related update file yourself, and you can figure out which of those updates you trust or don't trust by yourself. If you're going to ignore the work people did, then you're going to have to redo that work yourself. This should come as no surprise. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v04011701b37c74eab67f>