On Sat, Feb 21, 2009 at 10:45 AM, Evan Fuller <fuller.e...@gmail.com> wrote: > > I have issue with both the idea and implementation of password-less > access. I don't understand how it works well, but it seems a lot like > keeping your password in an unencrypted file--if someone got access to > my computer for a short time (e.g. via some uncaught spyware) and > copied the public key, they could access my files anytime until I > realized it and changed the key.
That is absolutely correct. However, even if you *don't* use password-less access, somebody who gets access to your computer "for a short time (e.g. via some uncaught spyware)" could also easily run a key logger and steal all passwords you type when connecting to remote computers. > However, if this is the way to do > things, I'll take that risk. Is there a more user-friendly (Windows) > guide to this? I've been trying to set up the keys both manually on > the server and with the built-in function on SSH Secure Shell Client > 3.2.9. When I create the keys manually on the server, change > permissions, then transfer them to my computer, I get the error > "failed to read your public key...". On the other hand, when I use > the client to create the keys and upload to the server, it says > everything is working properly, but then fails to actually authorize > to connect and still prompts for password. I've tried variations > (using .ssh or .ssh2, subdirectories) to no avail. The server OS is > SunOS 5.8. You should only ever create keys on the client -- keys are not needed on the server. SunOS 5.8 is pretty old and to get passwordless login to work, especially with old ssh servers, it's critically important that the ssh versions match up, that both support common protocols, and that all permissions are right for the files on the server (i.e., the ssh directory is only readable by you, etc.) This is usually very easy if the server is a recent linux, OS X or Sun OS, but 5.8 is pretty old, and it can be very frustrating. Unfortunately we'll probably never support Sage on SunOS 5.8, or you could just run sage there and window it back. I can now see very much how for you having an interactive password for the server= option in sage would be very nice. I may look into implementing this again today -- it might be very easy. - - william > > Thanks, > Evan > > On Feb 20, 7:16 pm, William Stein <wst...@gmail.com> wrote: >> On Fri, Feb 20, 2009 at 4:40 PM, Evan Fuller <fuller.e...@gmail.com> wrote: >> >> > I'd like to be able to have SAGE use the copy of mathematica on my >> > department server, which requires SSH with password. Looking at >> > previous posts, it sounds like there is no way to do this without >> > setting up somethingpassword-less. I'm hoping there has been an >> > improvement on this in the 18 months since those posts. Can anyone >> > help me out? I'm using the latest version binary (3.2.3) on Windows, >> > in case that's relevant. >> >> Why don't you setuppassword-lessssh access to your department server? >> Is there some reason you don't, except that perhaps you don't know how? >> It's very easy as long as your department is running a Linux server. What is >> the exact OS they are using? >> >> -- William > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
