Result for 070BEBA30B1F26B26BEFCE29FB0C27FFAC90EB16

Query result

Key Value
FileName./usr/share/doc/twine/html/_sources/index.rst.txt
FileSize675
MD5C823AA8C6E839491469FC88354502C11
SHA-1070BEBA30B1F26B26BEFCE29FB0C27FFAC90EB16
SHA-256E20FD7F2006DA8F286F9694BB0FD73EEACA43113FEB09C9396C80B95012F2F69
SSDEEP12:cAVM+Ra0Q00nCT2r2zWdYz6foGlTVzKvmhsIDptEoOqdp1Bp/oZ6NhZmsM:c4M+Rq0d2YWwkZ2ipaoOqddpAULu
TLSHT100010238FD9817116A93C5BE22737467E357B4AE3225640B316C12C8399E73627EF0E4
hashlookup:parent-total3
hashlookup:trust65

Network graph view

Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize42244
MD5CF8D6A0DE8E0665BFF1A5B7984BA760C
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).
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNametwine
PackageSectionutils
PackageVersion1.10.0-1
SHA-12071A361E2A87D14BE9EE165B830DB5D179ABD8B
SHA-256911E496F36B24FD3C98318D1022D02D37976AE9E818500893AB297F1DA4DF999
Key Value
FileSize57584
MD531B1BEE87D4E18DF063A75112232DD23
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).
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNametwine
PackageSectionutils
PackageVersion3.1.1-1
SHA-12E8B4CE28D00C5AB3DBE44EB1D143AED2BD2F185
SHA-2564BF39BC086906882B1DF4427251C61D0EB29AFDCC57790676D03CC1DD400BA43
Key Value
FileSize70168
MD5149C979B9B139B52D6146C43C5FE51E8
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.13.0-1
SHA-1C78E5302DFEE7D1982982A1CC04BEC5AA1545029
SHA-25656B66489D76F20CA31441CEAE4DA6D233469459CDBDEF7B2472B2690644B222C