Result for 58E4DD233029E690AE5EC696EBA292B740D99F2F

Query result

Key Value
FileName./usr/share/man/man3/Session::Storage::Secure.3pm.gz
FileSize6020
MD52B23D02889A9BE36241BED181638ECDC
SHA-158E4DD233029E690AE5EC696EBA292B740D99F2F
SHA-256F372374929306D1BB1381B24BA6F31101E4193C5120D8594656ADE37240F50B9
SSDEEP96:syz8TkjPUjUKkt654M9UnGUCQ4GrIzM3EDz1rttjl3HL29eBw65r8HdPOEc609:Tz8Y2w24M9hUCQ4GrmvDzn3K9e5r8Hty
TLSHT134C17D51D6B5FE33E2A777C89C8A452A4F388C192CC5814A680E86D1BA3EC8283947E1
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
MD5A388616288E1141CBEF42EAB72C62B74
PackageArchnoarch
PackageDescriptionThis module implements a secure way to encode session data. It is primarily intended for storing session data in browser cookies, but could be used with other backend storage where security of stored session data is important. Features include: * Data serialization and compression using Sereal * Data encryption using AES with a unique derived key per encoded session * Enforced expiration timestamp (optional) * Integrity protected with a message authentication code (MAC) The storage protocol used in this module is based heavily on at http://www.cse.msu.edu/~alexliu/publications/Cookie/Cookie_COMNET.pdf by Alex Liu and others. Liu proposes a session cookie value as follows: user|expiration|E(data,k)|HMAC(user|expiration|data|ssl-key,k) where | denotes concatenation with a separator character E(p,q) is a symmetric encryption of p with key q HMAC(p,q) is a keyed message hash of p with key q k is HMAC(user|expiration, sk) sk is a secret key shared by all servers ssl-key is an SSL session key Because SSL session keys are not readily available (and SSL termination may happen prior to the application server), we omit 'ssl-key'. This weakens protection against replay attacks if an attacker can break the SSL session key and intercept messages. Using 'user' and 'expiration' to generate the encryption and MAC keys was a method proposed to ensure unique keys to defeat volume attacks against the secret key. Rather than rely on those for uniqueness (with the unfortunate side effect of revealing user names and prohibiting anonymous sessions), we replace 'user' with a cryptographically-strong random salt value. The original proposal also calculates a MAC based on unencrypted data. We instead calculate the MAC based on the encrypted data. This avoids an extra step decrypting invalid messages. Because the salt is already encoded into the key, we omit it from the MAC input. Therefore, the session storage protocol used by this module is as follows: salt|expiration|E(data,k)|HMAC(expiration|E(data,k),k) where | denotes concatenation with a separator character E(p,q) is a symmetric encryption of p with key q HMAC(p,q) is a keyed message hash of p with key q k is HMAC(salt, sk) sk is a secret key shared by all servers The salt value is generated using Math::Random::ISAAC::XS, seeded from Crypt::URandom. The HMAC algorithm is 'hmac_sha256' from Digest::SHA. Encryption is done by Crypt::CBC using Crypt::Rijndael (AES). The ciphertext and MAC's in the cookie are Base64 encoded by MIME::Base64 by default. During session retrieval, if the MAC does not authenticate or if the expiration is set and in the past, the session will be discarded.
PackageNameperl-Session-Storage-Secure
PackageRelease1.12
PackageVersion1.000
SHA-10EF0E6921ADE676A64676C05687EC9CC4C7C5DB7
SHA-25603C9A76A5FEE4711D0645A75F3910D29E546937D24086CD24CE88870EBE46530