Key | Value |
---|---|
FileName | ./usr/share/doc/python-flask-kvsession-doc/html/objects.inv |
FileSize | 437 |
MD5 | 6B875E7F9AD514E09679940781937D8D |
SHA-1 | 2823052B182CD35E172EFA9E2B8D5CA869566C77 |
SHA-256 | B9D2009C78AE8950772AC1AA20A2288CABBDB86ADEAEA0D31DFEC8A9BFE5DFDB |
SSDEEP | 12:gVEtW9z/7ip+528f0XwuvrUgLzKENXHgi6LgMY:7W9bwY1f0XvrUuzKEJcLgMY |
TLSH | T1FFE0232471514B24225281D6607BF128E3B7012C5D750F784A1414EDD700C355B20DC0 |
hashlookup:parent-total | 2 |
hashlookup:trust | 60 |
The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 35784 |
MD5 | 9FEA43A7A5A619223EE706DD3804BD5F |
PackageDescription | Flask's session handling using server-side sessions (common documentation) This package contains server-side session replacement for Flask's signed client-based session management. Instead of storing data on the client, only a securely generated ID is stored on the client, while the actual session data resides on the server. . This has two major advantages: - Clients no longer see the session information - It is possible to securely destroy sessions to protect against replay attacks. . Other things are possible with server side session that are impossible with clients side sessions, like inspecting and manipulating data in absence of the client. . This is the common documentation package. |
PackageMaintainer | Kali Developers <devel@kali.org> |
PackageName | python-flask-kvsession-doc |
PackageSection | doc |
PackageVersion | 0.6.3+git20150814.1.83238b7-1~jan+nus1 |
SHA-1 | 597A5C28D7C47D7A9F8D25832BD4866AB889D19A |
SHA-256 | A8E717FA6F743C3510212619814FFD5CB58DFEDF35B883C96CB494D7AF6482E8 |
Key | Value |
---|---|
FileSize | 37032 |
MD5 | 7A4A15B306927726F7787A4C9B9E527F |
PackageDescription | Flask's session handling using server-side sessions (common documentation) This package contains server-side session replacement for Flask's signed client-based session management. Instead of storing data on the client, only a securely generated ID is stored on the client, while the actual session data resides on the server. . This has two major advantages: - Clients no longer see the session information - It is possible to securely destroy sessions to protect against replay attacks. . Other things are possible with server side session that are impossible with clients side sessions, like inspecting and manipulating data in absence of the client. . This is the common documentation package. |
PackageMaintainer | Kali Developers <devel@kali.org> |
PackageName | python-flask-kvsession-doc |
PackageSection | doc |
PackageVersion | 0.6.4+git20150814.1.83238b7-0kali1~jan+nus3 |
SHA-1 | 774D6B02B5A3F675EB9D92CD683A3A972831BDB9 |
SHA-256 | D2D5CB24F0919A7500F0F9CC203177FD631E3DCAB544CEFD1F4A956AE7FF5944 |