Bittorrent downloads for pfsense
-
Will there ever be torrents published for PFSENSE? Some days downloading from the mirrors is a bit slow, and with BT I can usually get an iso in half the time I can get it from a mirror.
Just a thought. Would be cool if updates could be distributed that way as well. But the last thing we need is to add bloat to pfsense itself.
-
IMHO: that means getting the pfSense from on unidentified source.
I guess that will never happen. And If I see one, I would never download it for that reason.
Mirrors exists because they are syncing with the official source - and no one else.
Note that 'mirrors' often propose more then only pfSense. Thousands of projects uses mirrors, so they are always busy.
I have nothing against "Bittorrent" but I would never use it to download an executable. Other type of files, ok ;)
-
If the RELEASE announcement is PGP signed and contains the hashes of the distributions, bittorrent would be fine. There's at least something to check against.
I see this as a non-starter since pfSense is so small.
pfSense-LiveCD-2.2-RC-amd64.iso.gz 2014-12-09 23:45 84M
-
I see this as a non-starter since pfSense is so small.
Exactly, it's not big enough that it matters. And most downloads after the initial install are auto-update anyway. If we were putting out multi-GB DVD ISOs, that'd be a different matter. Not likely we'll do bittorrent downloads.
-
IMHO: that means getting the pfSense from on unidentified source.
I guess that will never happen. And If I see one, I would never download it for that reason.
Mirrors exists because they are syncing with the official source - and no one else.
Note that 'mirrors' often propose more then only pfSense. Thousands of projects uses mirrors, so they are always busy.
I have nothing against "Bittorrent" but I would never use it to download an executable. Other type of files, ok ;)
The official mirrors could have the BitTorrent file. Torrent files contain SHA1-160 for each block, and each block size is known, so you can't just pad block sizes to more easily forge a SHA1. As someone else has pointed out, one could just verify the final image's SHA256 with what's on the site.