Result for D2E1142EC8823F81A91480938363F6A98234E1F6

Query result

Key Value
CRC32280C83FA
FileNamePKG-INFO
FileSize3019
MD5123A4718A24F1BFB3727E56E362E0237
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '80648', 'OpSystemCode': '51', 'ProductCode': '183361', 'ProductName': 'Scientific Linux DVD 2', 'ProductVersion': '6.9-i386'}
SHA-1D2E1142EC8823F81A91480938363F6A98234E1F6
SHA-256162A753FD3A853A3D8868CCBD9FC84686C9AA2A8032A8B8FE82F00E3B4A7E698
SSDEEP48:DF05ltN2bxmUUOkYJvY8ql1NCXcXep3CoHBoAEfnywcsXUeqMwiaas/:DF05lD2buOPvfqVCsupyoHBoAfZsXUV7
SpecialCode
TLSHT171514F2669D576F443E3048E819E8255AB1A87376A092CACFCAD830C5F61B76823D1BC
dbnsrl_modern_rds
insert-timestamp1647054301.5425713
sourceNSRL
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
MD59309FA06F2D181983F0A9F38CB500E98
PackageArchnoarch
PackageDescriptionThe Secure Sockets layer is only actually secure if you check the hostname in the certificate returned by the server to which you are connecting, and verify that it matches to hostname that you are trying to reach. But the matching logic, defined in RFC2818, can be a bit tricky to implement on your own. So the ssl package in the Standard Library of Python 3.2 now includes a match_hostname() function for performing this check instead of requiring every application to implement the check separately. This backport brings match_hostname() to users of earlier versions of Python. The actual code inside comes verbatim from Python 3.2.
PackageMaintainerFedora Project
PackageNamepython26-backports-ssl_match_hostname
PackageRelease5.el5
PackageVersion3.4.0.2
SHA-1C11668C3FCE7AD1692614AB932BC9D823805CB84
SHA-2566E89E290A5D491A9A1C590B4FDC1358E459E23ABAA740CA1BDDBBE1E4E7CF75A