neutral
deluge-1.3.15-win32-py2.7.exe
- SHA-256
- d3f7d371b70ca10c7e912b9d3443fea3acd0c905aab4ac7799f02e65b58c8e59
Deluge BitTorrent Client · earlier release
The URL Deluge Team published for this release, and the SHA-256 of every file in it, so you can prove the copy you have is that one and not something else wearing the same name.
Deluge BitTorrent Client is now on version 2.2.0. An older build stops getting security fixes, so install one only when you have a reason: a plugin that broke, a machine that cannot run the new one, a bug you need to reproduce. If you just want Deluge BitTorrent Client, take the current version.
deluge-1.3.15-win32-py2.7.exe
Windows does this without installing anything. In PowerShell:
Get-FileHash .\deluge-1.3.15-win32-py2.7.exe -Algorithm SHA256
Compare what it prints with the value above. If they match, your copy is byte-for-byte the one Deluge Team published. If they do not, it is a different file, whatever it is called and wherever it came from. Paste a hash into the verifier and it will tell you which release it belongs to.
If PowerShell is blocked by policy on the machine, the same thing works from plain cmd with certutil -hashfile deluge-1.3.15-win32-py2.7.exe SHA256. On macOS or Linux it is shasum -a 256 deluge-1.3.15-win32-py2.7.exe.
Publishers retire old releases, and we do not host copies, so a link from an earlier version can stop working without notice. Two ways it fails: an honest 404, or — more confusing — the server answers normally but hands you the current downloads page instead of the file. If what arrives is a few kilobytes of HTML rather than an installer, that is what happened.
The hash on this page stays useful either way. It still identifies Deluge BitTorrent Client 1.3.15 wherever you find a copy, which is the whole point of publishing it: you can accept a file from somewhere else and still prove it is the one Deluge Team built.
Every Deluge BitTorrent Client release we index · where this data comes from