forwarded 648704 http://code.google.com/p/pam-encfs/issues/detail?id=7 tag 648704 -squeeze found 648704 0.1.4.4-4 thanks
2011/11/14 francois lallart <[email protected]>: > Package: libpam-encfs > Version: 0.1.4.1-4 > Severity: normal > Tags: squeeze upstream > > libpam-encfs does not read encfs's stderr and so, can't display any error > message from it. That's why we can't have any information from syslog, except > that message: > > pam_encfs[11974]: exitcode : 1, errorstring : Thanks for looking at this. I see login from a console the major source of information about login problems. However, I agree that auth.log line is not informative about the problem or how to look at it. I have opened an issue upstream about this, http://code.google.com/p/pam-encfs/issues/detail?id=7 to know upstream POV > This little patch copy stderr on stdout, verbose mode has to be disable as > pam-encfs will only read 512 characters from encfs output. Note that this has some drawbacks, - encfs verbose mode needs to be disabled. - Since STDERR is captured no info is shown at all when trying to login from a console. I consider the info shown when login from a console the major source of information in case of problems, so I am not happy with this way. As a fallback I proposed upstream to use something like errorstring : Login failure. Login from a console to see more info. Regards, -- Agustin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
