Supprimer le mot de passe du trousseau nm-applet sur ubuntu

Jérémy · #1

Avoir sa connexion wifi mais a chaque fois être obligé de rentrer le mot de passe du trousseau pour pouvoir se connecter, c'est un peu lourd, surtout quand vous êtes tout seul sur votre machine, nous allons donc automatiser tout ça grace à PAM qui gère l'authentification automatique.

Il vous faut avant tout installer ceci =>

Code:

build-essential
libtool
libglib2.0-dev
libgnome-keyring-dev
libpam0g-dev

Ensuite installez ceci pam_keyring.

Maintenant vous avez juste à configurer le fichier gdm dans /etc/pam.d/.

ajoutez à la fin du document =>

Code:

auth optional pam_keyring.so try_first_pass
session optional pam_keyring.so

Redémarrer et ça devrait marcher.

/////////////

Bon pour moi j'ai un petit soucis encore non résolu sur une de mes machines qui refuse les conventions

Code:

make all-recursive
make[1]: entrant dans le répertoire « /Downloads/pam »
Making all in src
make[2]: entrant dans le répertoire « /Downloads/pam/src »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /Downloads/pam/src »
Making all in man
make[2]: entrant dans le répertoire « /Downloads/pam/man »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /Downloads/pam/man »
make[2]: entrant dans le répertoire « /Downloads/pam »
make[2]: quittant le répertoire « /Downloads/pam »
make[1]: quittant le répertoire « /Downloads/pam »

Puis

Code:

Making install in src
make[1]: entrant dans le répertoire « /Downloads/pam/src »
make[2]: entrant dans le répertoire « /Downloads/pam/src »
test -z "/usr/libexec" || mkdir -p -- "/usr/libexec"
/bin/bash ../libtool --mode=install /usr/bin/install -c 'pam-keyring-tool' '/usr/libexec/pam-keyring-tool'
/usr/bin/install -c pam-keyring-tool /usr/libexec/pam-keyring-tool
test -z "/usr/..//lib/security" || mkdir -p -- "/usr/..//lib/security"
/bin/bash ../libtool --mode=install /usr/bin/install -c 'pam_keyring.la' '/usr/..//lib/security/pam_keyring.la'
/usr/bin/install -c .libs/pam_keyring.so /usr/..//lib/security/pam_keyring.so
/usr/bin/install -c .libs/pam_keyring.lai /usr/..//lib/security/pam_keyring.la
/usr/bin/install -c .libs/pam_keyring.a /usr/..//lib/security/pam_keyring.a
ranlib /usr/..//lib/security/pam_keyring.a
chmod 644 /usr/..//lib/security/pam_keyring.a
PATH="$PATH:/sbin" ldconfig -n /usr/..//lib/security
----------------------------------------------------------------------
Libraries have been installed in:
/usr/..//lib/security

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-Wl,--rpath -Wl,LIBDIR' linker flag
- have your system administrator add LIBDIR to `/etc/ld.so.conf'

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
make install-data-hook
make[3]: entrant dans le répertoire « /Downloads/pam/src »
( \
cd /usr/..//lib/security && \
ln -s pam_keyring.so pam_keyring_auth.so && \
ln -s pam_keyring.so pam_keyring_session.so \
)
ln: création d'un lien symbolique `pam_keyring_auth.so' vers `pam_keyring.so': Le fichier existe.
make[3]: *** [install-data-hook] Erreur 1
make[3]: quittant le répertoire « /Downloads/pam/src »
make[2]: *** [install-data-am] Erreur 2
make[2]: quittant le répertoire « /Downloads/pam/src »
make[1]: *** [install-am] Erreur 2
make[1]: quittant le répertoire « /Downloads/pam/src »
make: *** [install-recursive] Erreur 1

Pourtant tout m'avais l'air correcte dans la configuration :

Code:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking whether ln -s works... yes
checking for pkg-config... /usr/bin/pkg-config
checking for GLIB - version >= 2.0.0... yes (version 2.12.11)
checking for gnome-keyring-1... yes
checking GNOME_KEYRING_CFLAGS... -I/usr/include/gnome-keyring-1 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
checking GNOME_KEYRING_LIBS... -lgnome-keyring -lglib-2.0
checking for gnome_keyring_unlock in -lgnome-keyring... yes
checking security/pam_modules.h usability... yes
checking security/pam_modules.h presence... yes
checking for security/pam_modules.h... yes
checking for pam_syslog in -lpam... no
checking for gnome-keyring-daemon... /usr/bin/gnome-keyring-daemon
checking for kill... /bin/kill
configure: creating ./config.status
config.status: creating Makefile
config.status: creating man/Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

Jérémy · #2

Probleme résolu !! => Installez ce package depuis le pool de Debian

=> libpam-keyring_0.0.8-6_i386.deb

spear · #3

Bonjour,

J'en avait assez d'entrer mon mot de passe trousseau à chaque connection, j'ai donc réalisé la manip', tout c'est déroulé sans incident( j'ai également installé le package debian)
Seulement maintenant, il ne me demande plus le mdp trousseau mais ma clé WPA ( encore plus chia** !!) j'ai pas réussit a résoudre le problème...

je poste le contenu de mon fichier gmd au cas ou :

#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so
@include common-auth
@include common-account
session required pam_limits.so
@include common-session
@include common-password
auth optional pam_keyring.so try_first_pass
session optional pam_keyring.so

voila si qqn a une idée.
Merci

Guest-82 · #4

Bonjour,

je n'arrive pas a installer le dernier paquet deb:
apparemment ca entre en conflit avec gnome keyring

Una ide de solucion?

Javier

Supprimer le mot de passe du trousseau nm-applet sur ubuntu

#1