Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

Re: Editing remote *nix files from Windows?

by snoopy (Deacon)
on Dec 15, 2009 at 19:52 UTC ( #812924=note: print w/ replies, xml ) Need Help??


in reply to Editing remote *nix files from Windows?

Another possibility is to map a network drive via ssh on Windows.

The drive can be mapped via Putty.

There are several other approaches, including Dokan (a FUSE emulation for Windows).

Update: Thanks afoken, good point!

  • The Putty solution requires that a local Samba service is running on the remote machine. This is then tunnelled via ssh back to the Windows machine.
  • The Dokan and other FUSE family solutions are a different animal. These run directly over ssh and should be able to be used on just about any *nix machine that's serving ssh, without prior setup.


Comment on Re: Editing remote *nix files from Windows?
Re^2: Editing remote *nix files from Windows?
by afoken (Parson) on Dec 15, 2009 at 21:05 UTC

    Nice trick, but it requires Samba or the like on the remote unix machine installed and running -- something that rarely happens on a machine connected directly to the internet, and for a good reason.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
Re^2: Editing remote *nix files from Windows?
by afoken (Parson) on Dec 16, 2009 at 21:01 UTC

    Hmmm, things I forgot to wrote last time:

    • PuTTY comes with some very useful helper programs:
      PAgent
      A key agent, so you don't need to enter your password a billion times a day. Enter the key pass phrase once Windows loads PAgent, and PuTTY will be able to use the key without any prompts.
      PSCP
      A simple command line scp client, sufficient for small batch jobs or perl scripts. Can use PuTTYs saved sessions and the keys from PAgent.
      PSFTP
      A command line sftp (not FTP!) client, sufficient for occasional file transfers. Like PSCP, it can use saved sessions and the keys from PAgent.
      PLink
      A command line ssh client, "PuTTY without the terminal emulator". Usually called from batch jobs or scripts to invoke remote programs or to create an SSH tunnel.
      PuTTYGen
      A ssh key generator, uses its own format and can export / import OpenSSH and ssh.com formats
    • There is a companion program called WinSCP, it can import PuTTYs sessions and can use the keys from PAgent. Basically, it is a graphical SCP and SFTP client, but can also talk plain old FTP. Recent versions also have a very limited command line window (without full terminal emulation) and a useable text editor for remote files. It can behave either like a Windows Explorer window or like a graphical clone of the Norton Commander.
    • From lots of experience, I would recommend to create a private key, export it to the remote system, and DISABLE password logins via SSH on the remote system. A nice side effect is that you don't have to type passwords any more, but the real benefit is that no one will be able to login via SSH to the remote machine, even if he correctly guesses login and password.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://812924]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (19)
As of 2014-07-31 14:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (249 votes), past polls