* Skip Morrow wrote: > I know that I should use ssh instead of telnet and scp instead of ftp. The > problem is, windows clients are kinda hard to come by for scp. Yeah, I know
True, true... > of several, but at work, it takes an act of congress to install anything on > the computers. So, what about https? I want to be able to grab files off > of my home computer while at work. The easy answer is to run an ftp server. > But I won't, for obvious reasons. I can run sshd, and I do, but I have the > afore-mentioned problem. If I set up apache with SSL, can I set up a secure > web page that asks for a password that will allow me to browse my file > system? Then I could use any up-to-date web browser to grab my files. Good > idea? Bad idea? Bad, but not as bad as FTP? Good, but not as good as > SCP/SSH? Well, with HTTPS you can only _get_ the files. You won't be able to synchronise them or upload any files. There's nothing bad about it I think.... For securing your directories on the webserver you should use .htaccess files. -- Best regards, Marc Herbrechter http://www.zebroc.de/ "It's hard to stay mad, when there's so much beautiy in the world. Sometimes I feel like I'm seeing it all at once and it's too much. My heart fills up like a balloon that's about to burst. And then I remember to relax and stop trying to hold on to it. And then it flows through me like rain and I can't feel anything but gratitude for every single moment of my stupid little life." - Alan Ball
