Result for 3D32D47E3020FC64D75718D3DF74B765596D453A

Query result

Key Value
FileName./usr/share/doc/twine/copyright
FileSize3025
MD5D32AD3718F07CC544B5CE5728E318B38
SHA-13D32D47E3020FC64D75718D3DF74B765596D453A
SHA-2565E369EC9AC999B27B864310E10D68D794CE83AD440106EEAEA6A4FF31313B470
SSDEEP48:ztXpEKjv4E3qR8piPlG3MRIzMp+ZVfzY4OX0ehzH31cSn7tVqbyVmyvHqYX0P:zTRjJdz3YIwSbY4gPzHFcS5VqGPEP
TLSHT19B51A49E25C482770B8019D47D96D4CAE31FAAB8B9FCD1E4E5580627D70CE3622E94E0
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
FileSize56492
MD5C712A58782390E7B86FD6C58AA44E5BB
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.3.0-1
SHA-13DF2C3D00EEB87CB7DABB7BEF9308476DF0F6C42
SHA-256F1551D36609517253EB74A1BDA44D5E182297A49BD8958147EC4E4BD6750C0F9
Key Value
FileSize70280
MD52E9798CE244FC783EDED2AD07EDC5F49
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).
PackageMaintainerDebian Python Team <team+python@tracker.debian.org>
PackageNametwine
PackageSectionutils
PackageVersion3.3.0-1
SHA-17FAC65974B1376969174A717BC033D4E05C8C2E9
SHA-256F0BE66878DBE26BE387D2B70F9B09034D527F3374D1DB9368721615D718AC16A