| Key | Value |
|---|---|
| FileName | ./usr/lib/python3.10/site-packages/trustme/__pycache__/_cli.cpython-310.pyc |
| FileSize | 2618 |
| MD5 | 06C282FEEB536602465A548FD11C014D |
| SHA-1 | 1C5C5330CA8D57319948D3F6813A6CDE03EA5FF6 |
| SHA-256 | A004AC64CFEE8065F5AEEECEC91FC2271900DCEEEE22B0090E62C6B6A738D81C |
| SSDEEP | 48:uH4Y7YmnsyOMICEU2+T+c1r5SwMHs8Kh5VjwmriAImaC5NAk9kdwcU7V/:ul7tnsyiaCSr5SI5rrDIA5NBGuc+ |
| TLSH | T1AB51F947D4813A33FDA3FB74789AC2207236D31C535B7A22AA0A62536F293D927096C0 |
| hashlookup:parent-total | 1 |
| hashlookup:trust | 55 |
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 |
|---|---|
| MD5 | B723D3A836032988CDC8B9D555414CF1 |
| PackageArch | noarch |
| PackageDescription | You wrote a cool network client or server. It encrypts connections using TLS. Your test suite needs to make TLS connections to itself. Uh oh. Your test suite probably doesn’t have a valid TLS certificate. Now what? trustme is a tiny Python package that does one thing: it gives you a fake certificate authority (CA) that you can use to generate fake TLS certs to use in your tests. Well, technically they’re real certs, they’re just signed by your CA, which nobody trusts. But you can trust it. Trust me. |
| PackageMaintainer | umeabot <umeabot> |
| PackageName | python3-trustme |
| PackageRelease | 3.mga9 |
| PackageVersion | 0.9.0 |
| SHA-1 | 2DC52DF03C1C2FE583EF3CA077F6CBF009EF1884 |
| SHA-256 | 4EE32CBF7AB2E43C4D80309B31090BC28CC17400E1CE3A667ADFD101F70A3346 |