Subject: Re: PINE-INFO digest 879

From: Matt Ackeret <[email-masked]>
Date: Fri, 15 Sep 2000 15:46:34 -0700 (PDT)

>From: Walt Smith <[email-masked]>
>These controls are not Pine-dependent, but are really emulator-specific.  
>I don't know if it's possible to remap emulator keystrokes in your setup,
>but this is about the only way you'll accomplish what you want.

How is this emulator specific?  The original questioner was talking about
the pico keystrokes.  (I presume it's still pico keystrokes even in the
headers..  I turned on the alternate editor as fast as I could when I started
using pine.  It would be torture if I had to use pico.)

>From: Eduardo Chappa <[email-masked]>
>*** Walt Smith ([email-masked]) wrote in the pine-info list
>about "Syntqax for inbox entries in pinerc or .pinerc files" today:
>
>:) Is there any way to include the password in these entries so as to avoid
>:) having to type them in when I want to access a remote mailbox?  For
>If this were possible it would be very unsecure, as the password would be
>in plain text, for anyone to read, the syntax does not support this, what

Yikes..  Why does the .pinerc have world-read privs?
  30 -rw-r--r--   1 mattack  users      15025 Sep  6 14:54 .pinerc

If *I* have read privs on the file, doesn't pine then run as my userid?
So if I chmod o-r .pinerc, wouldn't it _not_ be insecure?  At least people
couldn't casually read the password.

---

From: Eduardo Chappa <[email-masked]>
Date: Fri, 15 Sep 2000 20:23:13 -0700 (PDT)

*** Matt Ackeret ([email-masked]) wrote in the pine-info list about "Re:
PINE-INFO digest 879" today:

:) >If this were possible it would be very unsecure, as the password would be
:) >in plain text, for anyone to read, the syntax does not support this, what
:) 
:) Yikes..  Why does the .pinerc have world-read privs?
:)   30 -rw-r--r--   1 mattack  users      15025 Sep  6 14:54 .pinerc
:) 
:) If *I* have read privs on the file, doesn't pine then run as my userid?
:) So if I chmod o-r .pinerc, wouldn't it _not_ be insecure?  At least people
:) couldn't casually read the password.

It would still be insecure, if you ever leave your computer unattended,
your password will be there for any one to see, while you come back. It
has to be encripted.

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

---

From: Matt Ackeret <[email-masked]>
Date: Sat, 16 Sep 2000 15:04:12 -0700 (PDT)

>your password will be there for any one to see, while you come back. It

But you can say the same thing about leaving pine running..  it's "insecure"
since someone could come up and read your mail.

Or basically any computer running in an office building unless people
lock their accounts/log out every single time they leave their desk.

---

From: Eduardo Chappa <[email-masked]>
Date: Sat, 16 Sep 2000 15:14:13 -0700 (PDT)

:) On Fri, 15 Sep 2000, Eduardo Chappa wrote:
:) >It would still be insecure, if you ever leave your computer unattended,
:) >your password will be there for any one to see, while you come back. It
:) >has to be encripted.
:) 
:) But you can say the same thing about leaving pine running..  it's "insecure"
:) since someone could come up and read your mail.
:) 
:) Or basically any computer running in an office building unless people
:) lock their accounts/log out every single time they leave their desk.

Yes, you can say that. The point is not only that someone may read your
mail, is that they would have access to the computer where that e-mail is
stored. Steal all kind of information that is available to them, and all
in your name. I don't disagree with you at all, but a password may also
give them the chance to do anything they like whenever they like too.

---

From: Gopi Sundaram <[email-masked]>
Date: Sun, 17 Sep 2000 00:02:17 -0400 (EDT)

On Sat, 16 Sep 2000, Matt Ackeret wrote:

> But you can say the same thing about leaving pine running..  it's
> "insecure" since someone could come up and read your mail.

Basically, the idea is containment of damage. If someone got
administrative privileges on your network or computer through
unauthorized means, you should minimize the amount of information
available to him/her, despite the level of authority on the network.

Stallman has a fine book on applied crypto. There are some very
detailed descriptions of why things must be done certain ways. Take a
look at it if you care to.

Gopi.

-- 
Gopi Sundaram
[email-masked]

---

From: Antje Koschel <[email-masked]>
Date: Tue, 19 Sep 2000 10:32:24 +0200 (MET DST)

Hi,

I'm now testing pine in connection with an imapserver (courier-imap-1.0 +
qmail-1.03 + Maildirs).

How can I get an imap folder collection displayed in pine.
I tried the following:
folder-collections= imap-folder {imapserver}[INBOX.%]
        imap {imapserver}INBOX[],
        imap3 {imapserver}inbox.[]

It shows the folders as:
-------------------------------------------------------------------------------------
Folder-Collection <imap-folder>
-------------------------------------------------------------------------------------

INBOX.mail[.]	INBOX.sent-mail[.]
  
-------------------------------------------------------------------------------------
Folder-Collection <imap>
-------------------------------------------------------------------------------------

.mail[.]
.sent-mail[.]

-------------------------------------------------------------------------------------
Folder-Collection <imap3>
-------------------------------------------------------------------------------------

mail[.]
sent-mail[.]

Selecting one of them gives an error messages for all three formats:

[Can't find Incoming Folder INBOX.sent-mail.]

Why does it say  "incoming" folder?
And how do I have to define them?

The incoming folders are defined as:
incoming-folders=mail {imapserver}INBOX.mail,

And they are accessible.

Thanks,
Antje

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------