Joerg Barfurth wrote:
> Darren J Moffat schrieb:
>> Alan Coopersmith wrote:
>
>
>>> What will they need to do? (For some reason, the community xdm
>>> & gdm sources passes the X display as the PAM_TTY value, so we'd
>>> either need to change them or add :0 to /etc/securetty. From
>>> looking a
Darren J Moffat schrieb:
> Alan Coopersmith wrote:
>> What will they need to do? (For some reason, the community xdm
>> & gdm sources passes the X display as the PAM_TTY value, so we'd
>> either need to change them or add :0 to /etc/securetty. From
>> looking at the dtlogin code, it appears to
Alan Coopersmith wrote:
> Darren J Moffat wrote:
>> This check is currently implemented in login(1) rather than in a
>
> ...and in xdm, gdm, and dtlogin too...
>
>> PAM module where it really belongs.
>
> Yes! Please!
>
>> Solution
>>
>> This case proposes the introduction of a pam_sec
Joerg Barfurth wrote:
> Linux-PAM has officially (re)defined it that way - and of course that is
> what most community developers develop against:
>
> "PAM_TTY: The terminal name: prefixed by /dev/ if it is a device file;
> for graphical, X-based, applications the value for this item should be
Alan Coopersmith wrote:
> Darren J Moffat wrote:
>> This check is currently implemented in login(1) rather than in a
>
> ...and in xdm, gdm, and dtlogin too...
>
>> PAM module where it really belongs.
>
> Yes! Please!
+1
>> Solution
>>
>> This case proposes the introduction of a pam
Darren J Moffat wrote:
> This check is currently implemented in login(1) rather than in a
...and in xdm, gdm, and dtlogin too...
> PAM module where it really belongs.
Yes! Please!
> Solution
>
> This case proposes the introduction of a pam_securetty(5) module
> and the removal of the e
Please review the attached proposal and help with the outstanding issues
before I submit this as an ARC case.
Note that the Virtual Console project could end up depending on this
case but does not at this time.
--
Darren J Moffat
-- next part --
An embedded and charset-
