Re: Automation Sans Window Server
Re: Automation Sans Window Server
- Subject: Re: Automation Sans Window Server
- From: Axel Luttgens <email@hidden>
- Date: Wed, 16 Apr 2008 10:17:22 +0200
Le 16 avr. 08 à 04:42, Philip Aker a écrit :
[...]
May be time for me to learn how to ssh seeing as I've got several OS
X machines. This is my understanding:
1. Generate some tag files with ssh-keygen.
2. Put one of them in my home folder.
3. Transfer another kind to the home folder of the remote machines.
4. Thereafter I may ssh to the remote and then start using some
commands (of which variety I'm not sure).
Any corrections for the above?
Hello Philip,
Above steps (1 to 3) are the hard way for a first glance at ssh.
I mean, they may prove extremely useful for password-less ssh
connections, but they involve a forest of conventions that may hide
the tree.
Assuming your various machines are regular OS X ones, let's say the
remote box you want to connect to has a user named "philip", and
"remote.local" as rendezvous name.
On the remote box, just enable ssh from the sharing preference pane.
Then, on this box (the client box), just type:
ssh email@hidden
in Terminal.
You should then be prompted for the password of user "philip" on the
remote box (for a first connection, there will be some number
crunching and a question about the identity of the remote box itself;
the result will be a key stored in your ~/.ssh/known_hosts file, on
the client, that will be re-used upon subsequent connections for
verifying the identity of the remote box).
Once the password entered, you should now be running a shell on the
remote box, as user "philip", the shell being the one defined in
remote philip's account.
On the client, the ssh command now transparently gives you access to
the remote shell's standard streams.
The remote connection being opened and handled by the remote system-
wide launchd process, this has of course some consequences on the
context in which the remote shell is running. That said, any command
liable to be run from a shell is a candidate command...
Can I do the same from single user mode?
Do you mean running the client in single user mode and connecting to
the remote box? I guess so (but I never tried; will try once I have to
reboot some box).
What's a standard call for ssh-keygen?
Just noticed Simon already replied to that one.
I would add that there's no real standard, as everything strongly
depends on your needs. For example, if you are happy with an
interactive key creation as well as the command's defaults, then a
straight:
ssh-keygen
may prove OK.
HTH,
Axel
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden