Examine individual changes

From Gentoo Wiki
Abuse Filter navigation (Home | Recent filter changes | Examine past edits | Abuse log)
Jump to: navigation, search

This page allows you to examine the variables generated by the Abuse Filter for an individual change, and test it against filters.

Variables generated for this change

VariableValue
Whether or not the edit is marked as minor (minor_edit)
Edit count of the user (user_editcount)
2375
Name of the user account (user_name)
MGorny
Age of the user account (user_age)
250982948
Page ID (article_articleid)
115726
Page namespace (article_namespace)
510
Page title (without namespace) (article_text)
PAM
Full page title (article_prefixedtext)
Project:PAM
Action (action)
edit
Edit summary/reason (summary)
wipe the project
Old content model (old_content_model)
wikitext
New content model (new_content_model)
wikitext
Old page wikitext, before the edit (old_wikitext)
{{Project |Name=Pluggable Authentication Method maintenance |Description=Pluggable Authentication Method is the main authentication method supported by Gentoo; the PAM maintenance project maintain the related software. |Email=pam-bugs@gentoo.org |ParentProject=Project:Base |PropagatesMembers=No |Members={{Project Member |Developer=User:Robbat2 |Role=Member |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=Member |IsLead=No }} }} Pluggable Authentication Method is the main authentication method supported by Gentoo; the PAM maintenance project maintain the related software. == What is PAM == PAM stands for ''Pluggable Authentication Modules'', and refers to a framework for wrapping various low-level authentication methods and facilities in a single, mostly standardized API, originally designed and implemented by Sun Microsystems and, as of today, common for Linux distributions and other Unix and Unix-like operating systems (FreeBSD, NetBSD, Solaris, Apple Mac OS X, IBM AIX, HP-UX, etc.). PAM is a very flexible framework, allowing a wide range of different setups to be implemented, without having to add extra support in all the software that needs authentication capabilities. For instance, it's possible to get Dovecot (an IMAP server) to authenticate transparently against MySQL, PostgreSQL, LDAP, or system users, without having to add any specific code for that to Dovecot itself (on the other hand, Dovecot '''does''' implement specific code to authenticate users against various SQL databases, but that is another story). The drawback of such a flexible framework is that the system is quite complex and fragile, as there are three or four different pieces of software that are involved in authentication. For this reason, there are applications that even when providing PAM authentication support, also provide (or even prefer) alternative solutions, like specific authentication code for various databases and file formats, or even their own plug-ins for different authentication methods. As I said, there are three or four different pieces of software involved in authentication using PAM: ''the application authenticating'' (like Dovecot in the previous example), the <code>libpam</code> library (from now on ''the PAM implementation'' ), ''the PAM module'' (that might or might not be distributed with the PAM implementation), and eventually ''a backend service'' like an SQL database, LDAP or some other library used by the module. You can probably already understand that when we talk about the PAM implementation, we refer about one implementation of the PAM framework, that is not unique. There are, indeed, multiple PAM implementations: other than the proprietary ones provided by various operating systems, there are at least two main Free Software implementations, '''Linux-PAM''' (not to be fooled by the name, as this was used by FreeBSD 4.0, and still is used by Apple Mac OS X) released under double GPL-2/BSD-3 license, and '''OpenPAM''', developed for NetBSD, but also used by FreeBSD since 5.0 and (for a while at least) by ALTlinux. Albeit the two implementations are mostly API compatible (Linux-PAM provides some extra utility functions in a <code>libpam_misc</code> library), and at least in part ABI compatible, there are other differences too: Linux-PAM provides a set of default PAM modules, while OpenPAM does not provide but the two main modules ({{Path|pam_permit}} and {{Path|pam_deny}}). For this reason, OpenPAM requires at a minimum an extra software component: the modules themselves. Beside the default set of modules (if provided), there are a few extra modules to add support for authentication against software like MySQL, PostgreSQL, LDAP, and similar. These modules are the main flexibility feature of PAM framework, as it is possible to create modules to authenticate in new ways without redesigning the whole authentication support in the applications (like for instance smartcard or USB token authentication), for local services at least. Most of the modules, then, don't take care of authentication by themselves, but rely on backend software, either being a backend service like a database or LDAP server, or a library (like BDB). This increase complexity once again, as a bug, a regression or a file format change for such a service might break authentication for all the services configured to make use of it. This is for instance the case for BDB-based authentication: if the module changed the version of the library it links against, the old authentication database would be unusable. For further documentation about the maintenance of PAM packages, the handling of PAM-compatible packages in ebuilds, and the administration of PAM authentication, please refer to the resources offered by this project page. == Resources == Resources offered by the Gentoo PAM maintenance project include: * [[Project:PAM/Service files|Analysis of a PAM service configuration file]] * [[Project:PAM/Upgrade to 0.99|Linux-PAM 0.99 upgrade guide]] {{Migrated|originalauthors={{Dev|Flameeyes}}}}
New page wikitext, after the edit (new_wikitext)
Unified diff of changes made by edit (edit_diff)
@@ -1,46 +1,1 @@ -{{Project -|Name=Pluggable Authentication Method maintenance -|Description=Pluggable Authentication Method is the main authentication method supported by Gentoo; the PAM maintenance project maintain the related software. -|Email=pam-bugs@gentoo.org -|ParentProject=Project:Base -|PropagatesMembers=No -|Members={{Project Member -|Developer=User:Robbat2 -|Role=Member -|IsLead=No -}}{{Project Member -|Developer=User:Zlogene -|Role=Member -|IsLead=No -}} -}} -Pluggable Authentication Method is the main authentication method supported by Gentoo; the PAM maintenance project maintain the related software. -== What is PAM == - -PAM stands for ''Pluggable Authentication Modules'', and refers to a framework for wrapping various low-level authentication methods and facilities in a single, mostly standardized API, originally designed and implemented by Sun Microsystems and, as of today, common for Linux distributions and other Unix and Unix-like operating systems (FreeBSD, NetBSD, Solaris, Apple Mac OS X, IBM AIX, HP-UX, etc.). - -PAM is a very flexible framework, allowing a wide range of different setups to be implemented, without having to add extra support in all the software that needs authentication capabilities. For instance, it's possible to get Dovecot (an IMAP server) to authenticate transparently against MySQL, PostgreSQL, LDAP, or system users, without having to add any specific code for that to Dovecot itself (on the other hand, Dovecot '''does''' implement specific code to authenticate users against various SQL databases, but that is another story). - -The drawback of such a flexible framework is that the system is quite complex and fragile, as there are three or four different pieces of software that are involved in authentication. For this reason, there are applications that even when providing PAM authentication support, also provide (or even prefer) alternative solutions, like specific authentication code for various databases and file formats, or even their own plug-ins for different authentication methods. - -As I said, there are three or four different pieces of software involved in authentication using PAM: ''the application authenticating'' (like Dovecot in the previous example), the <code>libpam</code> library (from now on ''the PAM implementation'' ), ''the PAM module'' (that might or might not be distributed with the PAM implementation), and eventually ''a backend service'' like an SQL database, LDAP or some other library used by the module. - -You can probably already understand that when we talk about the PAM implementation, we refer about one implementation of the PAM framework, that is not unique. There are, indeed, multiple PAM implementations: other than the proprietary ones provided by various operating systems, there are at least two main Free Software implementations, '''Linux-PAM''' (not to be fooled by the name, as this was used by FreeBSD 4.0, and still is used by Apple Mac OS X) released under double GPL-2/BSD-3 license, and '''OpenPAM''', developed for NetBSD, but also used by FreeBSD since 5.0 and (for a while at least) by ALTlinux. - -Albeit the two implementations are mostly API compatible (Linux-PAM provides some extra utility functions in a <code>libpam_misc</code> library), and at least in part ABI compatible, there are other differences too: Linux-PAM provides a set of default PAM modules, while OpenPAM does not provide but the two main modules ({{Path|pam_permit}} and {{Path|pam_deny}}). For this reason, OpenPAM requires at a minimum an extra software component: the modules themselves. - -Beside the default set of modules (if provided), there are a few extra modules to add support for authentication against software like MySQL, PostgreSQL, LDAP, and similar. These modules are the main flexibility feature of PAM framework, as it is possible to create modules to authenticate in new ways without redesigning the whole authentication support in the applications (like for instance smartcard or USB token authentication), for local services at least. - -Most of the modules, then, don't take care of authentication by themselves, but rely on backend software, either being a backend service like a database or LDAP server, or a library (like BDB). This increase complexity once again, as a bug, a regression or a file format change for such a service might break authentication for all the services configured to make use of it. This is for instance the case for BDB-based authentication: if the module changed the version of the library it links against, the old authentication database would be unusable. - -For further documentation about the maintenance of PAM packages, the handling of PAM-compatible packages in ebuilds, and the administration of PAM authentication, please refer to the resources offered by this project page. - -== Resources == - -Resources offered by the Gentoo PAM maintenance project include: - -* [[Project:PAM/Service files|Analysis of a PAM service configuration file]] -* [[Project:PAM/Upgrade to 0.99|Linux-PAM 0.99 upgrade guide]] - -{{Migrated|originalauthors={{Dev|Flameeyes}}}}
Old page size (old_size)
5082
Lines added in edit (added_lines)
Lines removed in edit (removed_lines)
{{Project |Name=Pluggable Authentication Method maintenance |Description=Pluggable Authentication Method is the main authentication method supported by Gentoo; the PAM maintenance project maintain the related software. |Email=pam-bugs@gentoo.org |ParentProject=Project:Base |PropagatesMembers=No |Members={{Project Member |Developer=User:Robbat2 |Role=Member |IsLead=No }}{{Project Member |Developer=User:Zlogene |Role=Member |IsLead=No }} }} Pluggable Authentication Method is the main authentication method supported by Gentoo; the PAM maintenance project maintain the related software. == What is PAM == PAM stands for ''Pluggable Authentication Modules'', and refers to a framework for wrapping various low-level authentication methods and facilities in a single, mostly standardized API, originally designed and implemented by Sun Microsystems and, as of today, common for Linux distributions and other Unix and Unix-like operating systems (FreeBSD, NetBSD, Solaris, Apple Mac OS X, IBM AIX, HP-UX, etc.). PAM is a very flexible framework, allowing a wide range of different setups to be implemented, without having to add extra support in all the software that needs authentication capabilities. For instance, it's possible to get Dovecot (an IMAP server) to authenticate transparently against MySQL, PostgreSQL, LDAP, or system users, without having to add any specific code for that to Dovecot itself (on the other hand, Dovecot '''does''' implement specific code to authenticate users against various SQL databases, but that is another story). The drawback of such a flexible framework is that the system is quite complex and fragile, as there are three or four different pieces of software that are involved in authentication. For this reason, there are applications that even when providing PAM authentication support, also provide (or even prefer) alternative solutions, like specific authentication code for various databases and file formats, or even their own plug-ins for different authentication methods. As I said, there are three or four different pieces of software involved in authentication using PAM: ''the application authenticating'' (like Dovecot in the previous example), the <code>libpam</code> library (from now on ''the PAM implementation'' ), ''the PAM module'' (that might or might not be distributed with the PAM implementation), and eventually ''a backend service'' like an SQL database, LDAP or some other library used by the module. You can probably already understand that when we talk about the PAM implementation, we refer about one implementation of the PAM framework, that is not unique. There are, indeed, multiple PAM implementations: other than the proprietary ones provided by various operating systems, there are at least two main Free Software implementations, '''Linux-PAM''' (not to be fooled by the name, as this was used by FreeBSD 4.0, and still is used by Apple Mac OS X) released under double GPL-2/BSD-3 license, and '''OpenPAM''', developed for NetBSD, but also used by FreeBSD since 5.0 and (for a while at least) by ALTlinux. Albeit the two implementations are mostly API compatible (Linux-PAM provides some extra utility functions in a <code>libpam_misc</code> library), and at least in part ABI compatible, there are other differences too: Linux-PAM provides a set of default PAM modules, while OpenPAM does not provide but the two main modules ({{Path|pam_permit}} and {{Path|pam_deny}}). For this reason, OpenPAM requires at a minimum an extra software component: the modules themselves. Beside the default set of modules (if provided), there are a few extra modules to add support for authentication against software like MySQL, PostgreSQL, LDAP, and similar. These modules are the main flexibility feature of PAM framework, as it is possible to create modules to authenticate in new ways without redesigning the whole authentication support in the applications (like for instance smartcard or USB token authentication), for local services at least. Most of the modules, then, don't take care of authentication by themselves, but rely on backend software, either being a backend service like a database or LDAP server, or a library (like BDB). This increase complexity once again, as a bug, a regression or a file format change for such a service might break authentication for all the services configured to make use of it. This is for instance the case for BDB-based authentication: if the module changed the version of the library it links against, the old authentication database would be unusable. For further documentation about the maintenance of PAM packages, the handling of PAM-compatible packages in ebuilds, and the administration of PAM authentication, please refer to the resources offered by this project page. == Resources == Resources offered by the Gentoo PAM maintenance project include: * [[Project:PAM/Service files|Analysis of a PAM service configuration file]] * [[Project:PAM/Upgrade to 0.99|Linux-PAM 0.99 upgrade guide]] {{Migrated|originalauthors={{Dev|Flameeyes}}}}
New page text, stripped of any markup (new_text)
Parsed HTML source of the new revision (new_html)
<div class="mw-parser-output"> <!-- NewPP limit report Cached time: 20190923161552 Cache expiry: 86400 Dynamic content: false CPU time usage: 0.002 seconds Real time usage: 0.002 seconds Preprocessor visited node count: 0/1000000 Preprocessor generated node count: 2/1000000 Post‐expand include size: 0/2097152 bytes Template argument size: 0/2097152 bytes Highest expansion depth: 0/40 Expensive parser function count: 0/100 Unstrip recursion depth: 0/20 Unstrip post‐expand size: 0/5000000 bytes --> <!-- Transclusion expansion time report (%,ms,calls,template) 100.00% 0.000 1 -total --> </div>
Unix timestamp of change (timestamp)
1569255355