Subject: RE: compiling pine

From: Hong Tian <[email-masked]>
Date: Wed, 16 Oct 2002 15:58:45 -0400

Eduardo,

Pine works good after compiling SSL into it. I compiled with
PASSFILE='pinepass'. It looks that I need to create the "pinepass" file for
each users. We have hundreds of users. Should I create all hundreds of
"pinepass" files, or there may be a way to create only one "pinepass" file
on the top of root? Do you know the simple solution?

Thanks,
Hong

-----Original Message-----
From: Eduardo Chappa [mailto:[email-masked]]
Sent: Wednesday, October 16, 2002 12:21 PM
To: Hong Tian
Cc: Pine Discussion Forum
Subject: Re: compiling pine

*** Hong Tian ([email-masked]) wrote in the pine-info list today:

:) I use the same pine.conf as before. But I get error message as
:) followings: [Can't open mailbox
:) {exchange.ias.edu/ssl/novalidate-cert}INBOX: invalid remote
:) specification]

It looks like you did not compile SSL into it, if you want to know if SSL
is compiled into it, start pine as follows:

pine -supported

it will give you a list of drrivers, authenticators, etc that are
supported. At the very top, it should say:

Encryption:
  TLS and SSL

if it does not say that, then SSL was not added, and you should see why it
was so. Normally, pine will tell you either at the moment that compilation
starts why it can not add SSL (e.g. the ssl library is in the wrong
directory) or at the end it will tell you another message, of what it
found wrong, and you should try to solve those problems, otherwise, you
won't be able to add SSL support. If you don't care about ssl, and you
want to avoid seeing nasty error messages simply build pine as

build NOSSL xyz

(xyz is the code you need to enter).

-- 
Eduardo
http://www.math.washington.edu/~chappa/pine/

---

From: Eduardo Chappa <[email-masked]>
Date: Wed, 16 Oct 2002 13:22:07 -0700 (PDT)

*** Hong Tian ([email-masked]) wrote today:

:) Pine works good after compiling SSL into it. I compiled with
:) PASSFILE='pinepass'. It looks that I need to create the "pinepass" file
:) for each users. We have hundreds of users. Should I create all hundreds
:) of "pinepass" files, or there may be a way to create only one
:) "pinepass" file on the top of root? Do you know the simple solution?

Right, create a passfile for each user, or let every user create it by
themselves, do not create one for everybody, as it's very easy to decrypt
it if it falls in the wrong hands.  In PC-Pine a user has the ability to
specify the location of the password file from the command line, I have a
patch in my web page that allows you to do the same but for unix Pine (the
disadvantage is that the location of the password file, but not its
content, will be visible when you execute the "ps" command).

My advise would be that whatever you do, create a password file that will
be hidden from the view of the user, so that they can not tamper with it
in any way. Normally running a script as root that "touches" the password
file for every user should solve this problem for you, and this should be
fast.

---

From: "Timothy J. Luoma" <[email-masked]>
Date: Wed, 16 Oct 2002 16:38:15 -0400

Hong Tian wrote:

 > PASSFILE='pinepass'. It looks that I need to create the "pinepass"
 > file for each users. We have hundreds of users. Should I create all
 > hundreds of "pinepass" files, or there may be a way to create only one
 > "pinepass" file on the top of root? Do you know the simple solution?

You need one for each, I think.

cd /home
for i in *
do
touch $i/pinepass
chown $i.$i $i/pinepass
done

is how I would do it if all the user directories were under /home and 
you have UID = GID setup.

May need tweaking for your setup.

TjL

-- 
'Confessions of a browser sniffer' today on Beyond30
OperaBlog: Beyond30                      http://tntluoma.com/beyond30
30 Days to becoming an Opera Lover     http://www.tntluoma.com/switch
Opera Panels / Sidebars                  http://tntluoma.com/sidebars

---

From: Richard Stevenson <[email-masked]>
Date: Thu, 17 Oct 2002 09:53:19 +1300 (NZDT)

> You need one for each, I think.

How about this in /etc/profile (for sh-type shells; modify as necessary
for csh variants)?

if [ ! -e $HOME/pinepass ]; then
  touch $HOME/pinepass
fi

Cheers

R

-- 
Richard Stevenson
Systems Specialist
Xtra Limited
http://xtra.co.nz