| 1 |
В Пт, 22/03/2019 в 23:56 +0300, Andrew Savchenko пишет: |
| 2 |
--------------->%--------------- |
| 3 |
> > - Making pambase always install the configuration for |
| 4 |
> > pam_elogind.so, |
| 5 |
> > the same way it does for pam_gnome_keyring.so at this very moment, |
| 6 |
> > effectively removing elogind USE flag from it. |
| 7 |
> |
| 8 |
> Maybe that's a good time to make USE flag for pam_gnome_keyring.so. |
| 9 |
> Really, we shouldn't force users with some crap just "because it |
| 10 |
> doesn't hurt (much)". |
| 11 |
|
| 12 |
There used to be a gnome-keyring USE flag that controlled auto- |
| 13 |
launching of gnome-keyring-daemon on user login. But now support for |
| 14 |
gnome-keyring in pambase is pretty minimal, clearly not deserving a USE |
| 15 |
flag: |
| 16 |
|
| 17 |
$ portageq match / pambase |
| 18 |
sys-auth/pambase-20150213-r2 |
| 19 |
$ portageq contents / sys-auth/pambase-20150213-r2 | xargs grep |
| 20 |
gnome_keyring 2>/dev/null |
| 21 |
/etc/pam.d/passwd:-password optional pam_gnome_keyring.so |
| 22 |
use_authtok |
Archives