|
|
Security Threat
I assume it goes without saying that having passwords saved in potentially clear text [even a compiled Applescript is likely to not be safe since the username and password can probably be seen in a hexeditor] on your computer is a bad idea....
Security Threat
Yes pub/priv key is definitely the way to go...
SSHLogin
Just looked for SSHLogin on version tracker and it seems like it has vanished... The website is gone... (see version tracker)
shame, because it sounded good!
SSHLogin
Hmmm sshLogin has disappeard... supposedly either of these two items will do the same thing. I have not tried them though:
Another option (store password in keychain)
this applescript code will retrieve a password from the Keychain:
Use the Keychain Access application to create a new password with the name you chose ("Some Password" in the example). The "unlock" command will request your keychain password if the keychain is locked. If the keychain is already locked it won't ask.tell application "Keychain Scripting" tell keychain 1 unlock set theKey to first key whose name is "Some Password" set theUsername to (account of theKey) as string set thePassword to (password of theKey) as string end tell end tell ---
Security Threat
I use SSHKeychain. It keeps sshagent key passwords in the Keychain and turns them off if the screen saver is on. (Look for it on versiontracker)
Security Threat
Don't forget that any root on a machine you're connected has acces to all the box you can log on without password.
Security Threat
Well, root can become you and then get in that way. But the root user can't directly contact your host and get in using your public/private key.
Security Threat
To explain what I want to say a little more let's have a simple scenario. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.33 seconds |
|