Date: Sun, 16 Sep 2001 22:21:24 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Trevin Chow" <tmchow@sfu.ca> Cc: <questions@FreeBSD.ORG> Subject: RE: Passwordless Pine? Message-ID: <009601c13f38$98240360$1401a8c0@tedm.placo.com> In-Reply-To: <Pine.GSO.4.30.0109162145130.12245-100000@fraser.sfu.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
>-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Trevin Chow >Sent: Sunday, September 16, 2001 9:49 PM >To: Ted Mittelstaedt >Cc: questions@FreeBSD.ORG >Subject: RE: Passwordless Pine? > > >Hi Ted, > >Thanks for you input, but I *HAVE* been trying it out. I'm not sure why >you think I haven't. > Ah - when I asked if it worked with passwords, you didn't answer yes or no, insted responding with a question asking why it wouldn't work. What else would you expect me to think? >I attempted what you suggested from your own setup and I'm not even sure >if that's even opening an SSH connection to the IMAP mailserver. How do I >know if it's an SSH connection? > Ah, yes - very good question. Your not the only one annoyed that the developers of Pine didn't see fit to put up a message on screen indicating that SSH was in effect. What worked for me is to go to the mailserver and in inetd.conf, comment out the imap line, leaving only the imaps line. This turns off the non-SSHified IMAP server. imaps only responds to port 993 of course, so if the Pine client was switching to the regular IMAP server at port 143 behind my back then it would have failed. Ugly and crude, but effective. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >Trevin > > >On Fri, 14 Sep 2001, Ted Mittelstaedt wrote: > >> Trevin, >> >> Why oh why waste time speculating whether it would or wouldn't >> work when it's so simple to just TRY it out? >> >> Here's the relevant sections of MY own .pinerc: >> >> # Sets the time in seconds that Pine will attempt to open a UNIX secure >> # shell connection. The default is 15, min is 5, and max is unlimited. >> # Zero disables ssh altogether. >> ssh-open-timeout= >> >> # Sets the name of the command used to open a UNIX secure shell connection. >> # Tyically this is /usr/local/bin/ssh. >> ssh-path= >> >> # Sets the format of the command used to open a UNIX secure >> # shell connection. The default is "%s %s -l %s exec /etc/r%sd" >> # NOTE: the 4 (four) "%s" entries MUST exist in the provided command >> # where the first is for the command's path, the second is for the >> # host to connnect to, the third is for the user to connect as, and the >> # fourth is for the connection method (typically "imap") >> ssh-command= >> >> and here are the sections of my /usr/local/etc/pine.conf >> >> . >> . >> . >> # Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox >> # Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER). >> inbox-path={mail.mymailserver.com}inbox >> . >> . >> # Sets the time in seconds that Pine will attempt to open a UNIX secure >> # shell connection. The default is 15, min is 5, and max is unlimited. >> # Zero disables ssh altogether. >> ssh-open-timeout= >> >> # Sets the name of the command used to open a UNIX secure shell connection. >> # Tyically this is /usr/local/bin/ssh. >> ssh-path=/usr/bin/ssh >> >> # Sets the format of the command used to open a UNIX secure >> # shell connection. The default is "%s %s -l %s exec /etc/r%sd" >> # NOTE: the 4 (four) "%s" entries MUST exist in the provided command >> # where the first is for the command's path, the second is for the >> # host to connnect to, the third is for the user to connect as, and the >> # fourth is for the connection method (typically "imap") >> ssh-command= >> >> Note that I do NOT use "passwordless" connection via SSH to the IMAP >> server. This works just file to establish an SSH connection to the >> mailserver. >> >> My advice to you is to get it working the normal SSH way, then once you >> have it running then go off and try to get all the fancy passwordless >> stuff in SSH to work. One bite at a time is the way to solve problems. >> Speculating as to what should or shouldn't work without testing it is >> a waste of time. >> >> Ted Mittelstaedt >tedm@toybox.placo.com >> Author of: The FreeBSD Corporate >Networker's Guide >> Book website: >http://www.freebsd-corp-net-guide.com >> >> >> >-----Original Message----- >> >From: Trevin Chow [mailto:tmchow@sfu.ca] >> >Sent: Friday, September 14, 2001 8:18 AM >> >To: Ted Mittelstaedt >> >Cc: questions@freebsd.org >> >Subject: RE: Passwordless Pine? >> > >> > >> >I can't see why it wouldn't as long as the SSH key has *no* passphrase. >> >I'm just wondering how to setup Pine properly. >> > >> > >> >On Thu, 13 Sep 2001, Ted Mittelstaedt wrote: >> > >> >> Does Pine work properly with SSH _without_ it being passwordless? >> >> (ie: the normal SSH way?) >> >> >> >> Ted Mittelstaedt >> >tedm@toybox.placo.com >> >> Author of: The FreeBSD Corporate >> >Networker's Guide >> >> Book website: >> >http://www.freebsd-corp-net-guide.com >> >> >> >> >> >> >-----Original Message----- >> >> >From: owner-freebsd-questions@FreeBSD.ORG >> >> >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Trevin Chow >> >> >Sent: Thursday, September 13, 2001 3:57 PM >> >> >To: questions@FreeBSD.ORG >> >> >Subject: Passwordless Pine? >> >> > >> >> > >> >> >I have succesfully implement public/private SSH keys to allow >passwordless >> >> >SSH connectiosn between 2 hosts. I want to also allow for passwordless >> >> >IMAP connections via SSH in pine between one of the hosts to >the other. I >> >> >found this on teh net and thought it woudl be pretty easy: >> >> > >> >> >http://www.washington.edu/pine/pine-info/1999.12/msg00170.html >> >> > >> >> >However, whenever I load up pine and try to connect via IMAP, >it gives me >> >> >a timeout message and then prompts me for my password. >> >> > >> >> >I have a feeling it has to do with this configuration line in .pinerc: >> >> > >> >> >----------------- >> >> ># Sets the format of the command used to open a UNIX secure >> >> ># shell connection. The default is "%s %s -l %s exec /etc/r%sd" >> >> ># NOTE: the 4 (four) "%s" entries MUST exist in the provided command >> >> ># where the first is for the command's path, the second is for the >> >> ># host to connect to, the third is for the user to connect as, and the >> >> ># fourth is for the connection method (typically "imap") >> >> >ssh-command=%s %s -q -l %s exec /etc/r%sd >> >> >----------------- >> >> > >> >> >I have no idea if that command should be altered or not..any >ideas anyone? >> >> > >> >> > >> >> > >> >> >To Unsubscribe: send mail to majordomo@FreeBSD.org >> >> >with "unsubscribe freebsd-questions" in the body of the message >> >> > >> >> >> > >> > >> >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?009601c13f38$98240360$1401a8c0>