Pluggable Authentication Modules (Pam)

[ravi0537`]

PAM, is a mechanism to integrate multiple low-level authentication schemes into a high-level application programming interface (API). PAM can do many things for you but the primary focus is to authenticate your users. It also allows to set up the environment the users will work in. a user name and a password has to be provided by the user to authenticate himself and gain access to the system.

Need for PAM
PAM and PAM-aware applications reduce the complexity of authentication. With the use of PAM, the system administrator can choose to use the same user database for every login process of your system. PAM has a well defined API so that the PAM dependent appliations will not crash even when the system administrator changes the underlying settings for the PAM. PAM can be taken advantage of by the application programmers if their application requires some kind of authentication. In this case, much less programming is involved and you don't have to write a complete set of authentication functions. appropriate back end to store user names and passwords can be chosen by the system administrator.

Get the details here:
http://ftp.ofloopub/howtos/dev/Packt.Pub...c.2006.pdf
http://en.wikipediawiki/Pluggable_Authen...on_Modules

[britjet13]

As current authentication mechanisms evolve and as new authentication mechanisms are introduced, system entry services such as login, rlogin, and telnet must continually be customized to incorporate these changes. With the Pluggable Authentication Module (PAM) framework, multiple authentication technologies can be added without changing any of the login services, thereby preserving existing system environments. PAM can be used to integrate login services with different authentication technologies, such as RSA, DCE, Kerberos, S/Key, and smart card based authentication systems. Thus, PAM enables networked machines to exist peacefully in a heterogeneous environment, where multiple security mechanisms are in place. The PAM framework and the module interfaces provide pluggability for user authentication, as well as for account, session, and password management. login and other system-entry services can use the PAM architecture, and thus ensure that all entry points for the system have been secured.

[ambadkar priya]

As current authentication mechanisms evolve and as new authentication mechanisms are introduced, system entry services such as login, rlogin, and telnet must continually be customized to incorporate these changes.

With the Pluggable Authentication Module (PAM) framework, multiple authentication technologies can be added without changing any of the login services, thereby preserving existing system environments. PAM can be used to integrate login services with different authentication technologies, such as RSA, DCE, Kerberos, S/Key, and smart card based authentication systems.

Thus, PAM enables networked machines to exist peacefully in a heterogeneous environment, where multiple security mechanisms are in place. The PAM framework and the module interfaces provide pluggability for user authentication, as well as for account, session, and password management. login and other system-entry services can use the PAM architecture, and thus ensure that

[thematrix333]

I finished preparing the report. I have uploaded the file so that someone else can use it for a technical seminars.

thank you.

[vishnu147]

Hi,

Can I pls get more info about the project? I need to give a technical seminar at college.

Regards,

Christine.