I checked. Here are some inconvenient "facts" for you:
*
There is NOT EVEN ONE SINGLE SSL LINK on the above page!!!!!
Dude - you need to take yourself off this project. If you are more
interested in winning some stupid pride fight than protecting users of a
security product, you deserve no place on the team.
Let me quote YOUR OWN WORDS back to you:
" Instead of providing a not very secure HTTPS access to the files... "
You work on a security product, and you expect us to accept that because you
somehow believe the same security that protects every single other thing on
the web is "not very secure", that it's all fine and hunky-dory for you to
distribute yours over PLAIN UNAUTHENTICATED TEXT, and to expect us to USE
this unauthenticated code to verify it's own sigantures, which also come the
same way ()
Here's some more facts - just one tiny list...
ftp://ftp.gnupg.ca/
ftp://ftp.ring.gr.jp/pub/net/gnupg/
ftp://gd.tuwien.ac.at/privacy/gnupg/
ftp://mirrors.dotsrc.org/gcrypt/
ftp://ftp.jyu.fi/pub/crypt/gcrypt/
ftp://mirror.cict.fr/gnupg/
ftp://ftp.franken.de/pub/crypt/mirror/ftp.gnupg.org/gcrypt/
ftp://ftp.freenet.de/pub/ftp.gnupg.org/gcrypt/
...
and the list snakes on
Do not close this bug. Your emotions are too heated to be rational now.