- It's the applications, stupid
- Will a whitelist save personal computing?
- Thousands of Web sites under attack
- To solve the unsolvable problem
- Re-thinking the security of virtual machines
- Security Development Lifecycle trumps code complexity
- Is your Web site FIPS compliant?
- Computer security: Why have least privilege?
- Strategic security: Get a handle on authentication
- Control user installs of software
December 31, 2006 | Comments: (0)
Securely copy files
Use Putty's Pscp.exe to securely copy files between computers.
Everyone frequently needs to copy files to and from different computers, even over the Internet. I still see a lot of unsecured FTP used, when it should have been retired long ago. Consider instead any one of the hundreds of more secure alternatives.
My favorite? scp (Unix, Linux, BSD) or Pscp.exe (Windows). Scp and Pscp.exe using SSH to securely (encrypt files and authenticate destinations) copy files from one computer to another. Most Linux, Unix, and BSD hosts already have scp (secure copy). Windows doesn't have any default utilities like scp, but the programmers of Putty (the fantastic, free SSH Windows client), offer very similar Pscp.exe. You can download Putty or Pscp.exe here.
With scp or Pscp.exe you can copy files over temporary SSH tunnels between source and destination. The only problem is that at least one of the machines has to be running an SSH server/daemon. Most Unix, Linux, and BSD's have that (i.e. sshd). If you don't have one, follow my yesterday instructions on loading OpenBSD, and it will easily load an sshd service. Then you can use the OpenBSD box/image to copy files.
I like to copy Pscp.exe to \Windows\System32 and rename it scp.exe, so I can use scp in Unix, Linix, BSD, and Windows without thinking about it.
Syntax is basically like the DOS copy command:
scp [from where if not there] [what] [to where?]
but you have to add a logon name, the @ sign, and machine name/IP address for the remote machine, so the syntax is:
scp [from where if not there] [what] [logonname]@x.x.x.x:[to where?]
Examples of syntax, if I'm on the box I'm copying from:
scp *.* roger@192.168.4.1:/
scp frog.tar roger@www.banneretcs.com:/tmp
Examples of the syntax if I'm on the destination box:
scp roger@192.168.5.6:c:/files/toad.zip \Window\temp
scp roger@www.banneretcs.com:\tools\putty\*.* c:\newtools
Scp is free, works great across any TCP/IP network, across the network, and you can send it to customers to use, and automate in batch files and scripts.
Once you start using scp, you'll probably never use ftp again.
Posted by Roger Grimes on December 31, 2006 10:28 AM
RATE THIS ARTICLE:
-

- COMMENTS
FTP-SSL:
Standards never were ironed out for FTP SSL, so there are different implementations (for instance, Serv-U supports switches for the different conventions...); Sun appears to be ambivalent about it, pushing the latest NFS instead; and none of the browser manufacturers ever got around to supporting an "ftps://..." protocol for URIs (I guess the thinking being that you would encrypt the file if it was that confidential...)
But I'd still like to see it...
TOP STORIES
Sun to clarify JavaFX planMS's dev tool service packs
HP in talks to buy EDS
Developers' role shifting
MS: XP SP3 reboots OEMs' fault
Apple: iPhone out of stock
Can Sun rejuvenate Java?
Powerset unveils Google-killer
FBI worried about Cisco gear
AMD updates quad-core Opterons
ADDITIONAL RESOURCES

- Application Security: Threats and How to Counter Them
- Why Linux Threats Mean Business
- Minding the Machines: PC Disaster Recovery for the Enterprise

- Protect Your Data with SSL
- Prevent Your Next Microsoft Exchange Outage
- 11 Myths About Microsoft Exchange Backup & Recovery





