Result for 328A873089F09E3B79DA2DDA923D44858D3D7DEA

Query result

Key Value
FileName./usr/share/lintian/overrides/twine
FileSize117
MD55FDDC6222B139910E600C07DDC8A127B
SHA-1328A873089F09E3B79DA2DDA923D44858D3D7DEA
SHA-2568A177350E7D053C5B3172C775CC2A43162361F07728CE1523E6B4D1F6D0A09EE
SSDEEP3:S8SKRxevWq+c8mJsLZBJ8MRJsj5MLRBcVN4NKzgYn:SDKnevH7TWLbJ1sGLoVrn
TLSHT18DB022382280B2220028080C880E8202003803E2022000F8A0B003202808CF22EB2F38
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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
FileSize21510
MD536E0FA5B6EAAB1265F95E5175DEF21C2
PackageDescriptionutility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . The biggest reason to use twine is that python setup.py upload uploads files over plaintext. This means anytime you use it you expose your username and password to a MITM attack. Twine uses only verified TLS to upload to PyPI protecting your credentials from theft. . Secondly it allows you to precreate your distribution files. python setup.py upload only allows you to upload something that you’ve created in the same command invocation. This means that you cannot test the exact file you’re going to upload to PyPI to ensure that it works before uploading it. . Finally it allows you to pre-sign your files and pass the .asc files into the command line invocation (twine upload twine-1.0.1.tar.gz twine-1.0.1.tar.gz.asc). This enables you to be assured that you’re typing your gpg passphrase into gpg itself and not anything else since you will be the one directly executing gpg --detach-sign -a <filename>. . Features: . - Verified HTTPS Connections - Uploading doesn’t require executing setup.py - Uploading files that have already been created, allowing testing of distributions before release - Supports uploading any packaging format (including wheels).
PackageMaintainerZygmunt Krynicki <zygmunt.krynicki@canonical.com>
PackageNametwine
PackageSectionutils
PackageVersion1.5.0-1
SHA-1A583F031B00B3A39F2ECBEFD634E861192C66312
SHA-256082BDE111553EF2CDDEA209C16186AEE15AAAA6E585F06E7FF8768D7EB7EDE95
Key Value
FileSize37034
MD5407692CF5AA429BB4D812BB377782432
PackageDescriptionutility for interacting with PyPI Twine is a tool for uploading distributions (in the Python meaning) to PyPi. . Why should twine be used over the traditional approach? . The biggest reason to use twine is that python setup.py upload uploads files over plaintext. This means anytime you use it you expose your username and password to a MITM attack. Twine uses only verified TLS to upload to PyPI protecting your credentials from theft. . Secondly it allows you to precreate your distribution files. python setup.py upload only allows you to upload something that you’ve created in the same command invocation. This means that you cannot test the exact file you’re going to upload to PyPI to ensure that it works before uploading it. . Finally it allows you to pre-sign your files and pass the .asc files into the command line invocation (twine upload twine-1.0.1.tar.gz twine-1.0.1.tar.gz.asc). This enables you to be assured that you’re typing your gpg passphrase into gpg itself and not anything else since you will be the one directly executing gpg --detach-sign -a <filename>. . Features: . - Verified HTTPS Connections - Uploading doesn’t require executing setup.py - Uploading files that have already been created, allowing testing of distributions before release - Supports uploading any packaging format (including wheels).
PackageMaintainerPython Applications Packaging Team <python-apps-team@lists.alioth.debian.org>
PackageNametwine
PackageSectionutils
PackageVersion1.8.1-2
SHA-10BFDE72B3D27C8DCD1A3CC6CB3566C923E3C8929
SHA-2565D4B601608CDE8DB4B8C4675419DD9664126A52C599D6105BDB1BCD27A9004D3