День добрый, Вопрос в следующем имеются токены у разных юзеров у одного rutoken у дрогово etoken но работают они на одной машине по очереди. Конфиг /etc/pam.d/common-auth для rutoken выглядит вот так
# here are the per-package modules (the "Primary" block)
auth [success=2 default=ignore] pam_krb5.so minimum_uid=1000 debug try_pkinit pkinit_user=PKCS11:/usr/lib/librtpkcs11ecp.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_cap.so
# end of pam-auth-update config
# here are the per-package modules (the "Primary" block)
auth [success=2 default=ignore] pam_krb5.so minimum_uid=1000 debug try_pkinit pkinit_user=PKCS11:/usr/lib/libeTPkcs11.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_cap.so
# end of pam-auth-update config
То есть получается что rutoken и etoken используют разные библиотеки.
Пока что сделал так
# here are the per-package modules (the "Primary" block)
auth [success=3 default=ignore] pam_krb5.so minimum_uid=1000 debug try_pkinit pkinit_user=PKCS11:/usr/lib/librtpkcs11ecp.so
auth [success=2 default=ignore] pam_krb5.so minimum_uid=1000 debug try_pkinit pkinit_user=PKCS11:/usr/lib/libeTPkcs11.so
auth [success=1 default=ignore] pam_unix.so nullok_secure try_first_pass
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_cap.so
# end of pam-auth-update config
