Key | Value |
---|---|
FileName | ./usr/share/doc/python-flask-kvsession-doc/html/_sources/index.rst.txt |
FileSize | 3750 |
MD5 | 69BC4CBFADBBC947A98404C23C91955D |
SHA-1 | 220662E861A4475A2CAFAB1E42958C37570B186A |
SHA-256 | 1CC23EA9B5AE27DF8BD8D41A5B2BA9053FBEA3FBA4F9C8F77F8A8D48B7C993A0 |
SSDEEP | 96:uobq8lLTrlxhT9CqKek9gJJ8fuBAV5aBk:ZuKL/lxaqe9EPMok |
TLSH | T17971416E7E4A17710E16C0A574B700A5EBB6522CB216B102F0BE47E8237DFA5837D5BC |
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 |