[Touch-packages] [Bug 1666203] [NEW] pam_tty_audit failed in pam_open_session

2017-02-20 Thread Toru Ikezoe
Public bug reported: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2018-04-16 Thread Toru Ikezoe
** Description changed: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-02-13 Thread Toru Ikezoe
** Description changed: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-02-05 Thread Toru Ikezoe
Hi Don-san. I am able to reproduce with the following procedure. - vagrant init ubuntu/xenial64 vagrant ssh # at xenial64 on VM echo 'session required pam_tty_audit.so enable=*' | sudo tee -a /etc/pam.d/common-session - When 'vagrant ssh' from other terminal, it

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-02-03 Thread Toru Ikezoe
Thank you for your response. I tested on 16.04/xenial with below packages, but this issue still exists. libpam-modules-bin 1.1.8-3.2ubuntu2.1 linux-image-4.4.0-137-generic 4.4.0-137.163 This issue has been fixed on the PAM 1.2.0, but 16.04/xenial and 18.04/bionic used the

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

2019-05-10 Thread Toru Ikezoe
Hi Don-san. I tried test, but it not fixed. I tried building by source code of version 1.1.8-3.2ubuntu 2.2, it looks like the patch has not been applied. Can you check again? [VERIFICATION XENIAL] 1) Used vagrant init ubuntu/xenial64 to create new instance. 2) Used vagrant ssh to login. 3)