Result for 0DC6A80B128865C459EB2A1C8D39FDE5B43F0380

Query result

Key Value
FileName./usr/share/doc/twine/copyright
FileSize1679
MD5792B819CFCF640AE163A6F0D82B073B3
SHA-10DC6A80B128865C459EB2A1C8D39FDE5B43F0380
SHA-256FAC1C442D4EC0DEC7AC8D599FEF6006B2D6ECEF276A8DAE7EA8FBB1E3393760F
SSDEEP24:g0tEbpEKcmv4LiV4ITRkU0E+ohzHQk18ps+nxxTN30LVyROkHAITbVSnYNln0P:cbpEKjv42V4OX0ehzH31clZmyvHqYX0P
TLSHT15A31745D258093B70AC015D67D47C4CFE21BFA66B5ADC1909049828A862DA7602F51E0
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