Well, who damages LOGIN_CAP processing in sshd now? It not reads
~/.login_conf anymore and not sets LOGIN_CAP limits.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, Apr 20, 2002 at 05:21:42 +0400, Andrey A. Chernov wrote:
> Well, who damages LOGIN_CAP processing in sshd now? It not reads
> ~/.login_conf anymore and not sets LOGIN_CAP limits.
I see parent environment seriously damaged in do_setusercontext() since
not saved. I mean MAIL,BLOCKSIZE & FT
On Sat, Apr 20, 2002 at 06:43:05 +0400, Andrey A. Chernov wrote:
> On Sat, Apr 20, 2002 at 05:21:42 +0400, Andrey A. Chernov wrote:
> > Well, who damages LOGIN_CAP processing in sshd now? It not reads
> > ~/.login_conf anymore and not sets LOGIN_CAP limits.
>
> I see parent environment seriously
"Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> NOTE: I just commit the fix, see session.c commit log for detailed
> explanation.
Andrey, in the future please *submit patches for review*.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "uns
On Sat, Apr 20, 2002 at 17:12:21 +0200, Dag-Erling Smorgrav wrote:
> "Andrey A. Chernov" <[EMAIL PROTECTED]> writes:
> > NOTE: I just commit the fix, see session.c commit log for detailed
> > explanation.
>
> Andrey, in the future please *submit patches for review*.
This case is special - that
