Hmm, everytime I reply to you it doesn't indent with ">". strange. *******ing outlook. I need a beer. SSH clients for windows exist, I have quite a few at CryptoArchive (www|ftp.cryptoarchive.net). SSL ftp client for windows also exist, I rmember seeing at least one, can't remember the name offhand though. The SCP problem in SSH is quite deepseated as I understand it and I'm not entirely sure if they fixed it in 2.3.0 (have to check, groan). As for another poster: SSH/OpenSSH: SSH is the original, done by a finnish guy, it steadily got more and more commercial, 2.0 was 100% commercial, this sucked because it was so useful and not free. So OpenBSD team took 1.2.12 (or .22?) and ripped out all the proprietary code, cleaned it up a LOT, added ssh protocol 1.5 and 2 support, labled it OpenSSH, and everyone rejoiced =). =================== On Tue, 28 Nov 2000 01:55:45 -0700, you wrote:
BTW if you need people to login, and are worried about security then ftp is not your best bet. There are SSH and SSL ftp's though you might consider, or
For example? :-) I'd need also windows client support since users would access from a NT wks machine.
simply move to SSH and scp (which has it's own issues right now, sigh).
Yep, I've heard about these insecurities. Isn't there a secure (stable) version yet? Another question: what's the difference between the ssh and open-ssh packets which SuSE 6.4 ship with? Which one is recommended? =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ** RoMaN SoFt / LLFB ** roman@madrid.com http://pagina.de/romansoft ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com