[8441] in athena10

home help back first fref pref prev next nref lref last post

Re: [Debathena] #1087: pam_mitsecure

daemon@ATHENA.MIT.EDU (Debathena Trac)
Fri Sep 16 21:35:57 2011

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: geofft@mit.edu, jdreed@mit.edu, kaduk@mit.edu
Date: Sat, 17 Sep 2011 01:35:46 -0000
Reply-To: 
Message-ID: <052.3be7c96f6b90be8baa018cb5202fca27@mit.edu>
In-Reply-To: <043.eb61e0f16c69bf596adb778906427b7c@mit.edu>
Content-Transfer-Encoding: 8bit

#1087: pam_mitsecure-------------------------+--------------------------------------------------
 Reporter:  geofft       |       Owner:                    
     Type:  enhancement  |      Status:  new               
 Priority:  normal       |   Milestone:  The Distant Future
Component:  --           |    Keywords:                    
 See_also:               |  
-------------------------+--------------------------------------------------
Comment(by kaduk):
 Replying to [comment:1 jdreed]:
 > It's not entirely clear to me this is a good idea, or needed.  We've
 verified that putting NM in the gdm panel works to connect to MIT SECURE.
 Also, if you have a laptop, you should set up MIT SECURE once, and be done
 with it.  There's no good reason to have it be "on demand".  If there are
 issues about PAM's behavior at login time, I'd rather we put effort into
 making sure PAM has a better understanding of when it has network and when
 it doesn't.

 Er, is there a way to set up MIT SECURE "just once" that does not involve
 leaving my password or equivalent in a file on disk?  I haven't seen a
 whole lot of documentation on these things (though perhaps I haven't
 looked a whole lot), but I have negative interest in leaving my
 credentials sitting around like that.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/1087#comment:2>Debathena <http://debathena.mit.edu/>MIT Debathena Project

home help back first fref pref prev next nref lref last post