Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Issue after recent system update specrtre/meltdown [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
spsarolkar
n00b
n00b


Joined: 26 Jan 2018
Posts: 28

PostPosted: Mon Jan 29, 2018 2:08 am    Post subject: Issue after recent system update specrtre/meltdown [SOLVED] Reply with quote

HI,

I have just upgraded my system as per recommendation received in my gentoo box for amd64 spectre and meltdown patch. After upgrade it seems like someone kept the logging of PAM enabled. Every time I login bunch of messages gets printed on the console which are of no use to me, and they event don't show any issues :)

Thankfully,I get password prompt after that.

It looks like this breaks my i3lock, I have to login via ssh and kill the i3lock process to get access to my system.

The logs look like below

Code:
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_dispatch.c:_pam_dispatch_aux(198)] use_cached_chain=1 action=-1 cached_retval=0 retval=0
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_dispatch.c:_pam_dispatch_aux(106)] passing control to module...
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_dispatch.c:_pam_dispatch_aux(114)] module returned: Success
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_dispatch.c:_pam_dispatch_aux(155)] use_cached_chain is set to [1], but cached_retval == _PAM_INVALID_RETVAL
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_dispatch.c:_pam_dispatch_aux(198)] use_cached_chain=1 action=-1 cached_retval=0 retval=0
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_auth.c:pam_setcred(70)] pam_setcred exit
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_end.c:pam_end(15)] entering pam_end()
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_data.c:_pam_free_data(152)] called
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers(987)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers(995)] _pam_free_handlers: dlclose(/lib64/security/pam_env.so)
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers(995)] _pam_free_handlers: dlclose(/lib64/security/pam_unix.so)
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers(995)] _pam_free_handlers: dlclose(/lib64/security/pam_permit.so)
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers(995)] _pam_free_handlers: dlclose(/lib64/security/pam_limits.so)
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers(995)] _pam_free_handlers: dlclose(/lib64/security/pam_deny.so)
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_handlers.c:_pam_free_handlers_aux(1068)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_env.c:_pam_drop_env(94)] called.
[/var/tmp/portage/sys-libs/pam-1.2.1-r2/work/Linux-PAM-1.2.1/libpam/pam_end.c:pam_end(92)] exiting pam_end() successfully


I am not sure what else is broken apart from i3lock because of this. Can someone please help me turning them off.
_________________
SunilS


Last edited by spsarolkar on Mon Jan 29, 2018 10:34 am; edited 1 time in total
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 14159

PostPosted: Mon Jan 29, 2018 4:08 am    Post subject: Reply with quote

That output looks like you enabled PAM debugging. You probably do not want that. I do not know how this would have been activated as a side effect of general system upgrades, though. What is the output of emerge --pretend --verbose sys-libs/pam?
Back to top
View user's profile Send private message
spsarolkar
n00b
n00b


Joined: 26 Jan 2018
Posts: 28

PostPosted: Mon Jan 29, 2018 10:33 am    Post subject: Reply with quote

Hi Hu,

You are right the debug use flag was the cause of it. Thanks.
_________________
SunilS
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum