Result for 001526A2D1711720EC74917D992C6442EC5D71C1

Query result

Key Value
FileName./usr/share/man/man3/Catalyst::Authentication::Credential::Remote.3pm.gz
FileSize4484
MD51614433D17C3C906706CC0A4A1808627
SHA-1001526A2D1711720EC74917D992C6442EC5D71C1
SHA-2567D5D7ED3317A876F7304E560C8128BE6FD9BE07317F0BACD504960FA90F2389F
SSDEEP96:Y6w8+GR2w4d0YBGjScH61JxufOhmp2L8pvIHUSx3+1:Pw8+GR2wFPjS31CfeLWp1
TLSHT174916D978BB986D1B2EB3A6A08D7C12C63BB741FE27630C4319866C590DF5449133F43
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5DB5F4663D86A22A7926A56983CE65622
PackageArchnoarch
PackageDescriptionThe authentication plugin provides generic user support for Catalyst apps. It is the basis for both authentication (checking the user is who they claim to be), and authorization (allowing the user to do what the system authorises them to do). Using authentication is split into two parts. A Store is used to actually store the user information, and can store any amount of data related to the user. Credentials are used to verify users, using information from the store, given data from the frontend. A Credential and a Store are paired to form a 'Realm'. A Catalyst application using the authentication framework must have at least one realm, and may have several. To implement authentication in a Catalyst application you need to add this module, and specify at least one realm in the configuration. Authentication data can also be stored in a session, if the application is using the Catalyst::Plugin::Session module. *NOTE* in version 0.10 of this module, the interface to this module changed. Please see COMPATIBILITY ROUTINES for more information.
PackageNameperl-Catalyst-Plugin-Authentication
PackageRelease64.63
PackageVersion0.10023
SHA-133AB40B7A2EAFADB0214308803041703CBAFBB0C
SHA-256E34C23B66A260CDD7CAE5A9C176F06462FE9824AE26D3AFE207F858D7165E789