HTTPS support for downloading receiver files - Bounty: 10M DVC

[Traxo7]

Does daemon try to reach receiver files via https, or http? As one of the custodians is successfully listed as an IP address instead of a domain, I presumed issuing an SSL is not required (as SSL is probably not even allowed to be issued to IP addresses in the first place, or at least it might be a struggle to set up?).
In other words, should receiver file be reachable via https://... in addition to http://... ?

[DevElCuy]

There is support for https but the source code support is very outdated so it is not able to download anything from https. For that reason, we only list http hosts. We need to updated the source code with the most recent ssl libraries so that https can work. Also, this will allow us to host receiver files in many free public mirrors (i.e: github, gitlab, bitbacket, etc.), along the existing custodians, for ensuring resilience.

[DevElCuy]

UPDATE
Bounty reduced to 10M DVC see: #77 (comment)

ORIGINAL

Bounty
Since it is critical to have a reliable set of receiver files mirrors, I set a bounty of 50 million DVC from the DevFund to be distributed among all the people that work to fix this issue. The tester assigned is Qtera, which should certify the fix.

[DevElCuy]

Block 396000 (round 99) was found on 2019-10-26 11:07:49 and this is the record of custodians reporting sync:
(all dates are UTC)

2019-10-22 03:51:08 Custodian 1
2019-10-22 06:21:38 Custodian 2
2019-10-23 13:21:37 Custodian 3
2019-10-23 17:04:45 Custodian 4
2019-10-26 09:07:47 Custodian 5

Also Custodian 6 didn't report back, but http://devcoin.darkgamex.ch reports file creation date:

2019-10-22 05:49 Custodian 6

Custodian 7 never synced and now is offline.

I checked each mirror as custodians reported. Custodian 3 was working by then, it was not working for me on Oct 27th. If we discard Custodian 3 for not being reliable we still had 4 mirrors ready when Custodian 4 synced on 2019-10-23 17:04:45.

In conclusion, we had the custodians well setup 2 days and 18 hours in advance to round 99. Yet, we should define a safe deadline for syncing custodians.

[DevElCuy]

sawa reported a syncing issue with receiver 99 on https://bitcointalk.org/index.php?topic=233997.msg52886290#msg52886290

After starting the daemon, this message is displayed in the console:

Number of pages in getCommonOutputByText: 7
Insufficient identical pages in getCommonOutputByText.
Warning, writeFileText in receiver.h won't write the file:
/home/user/.devcoin/receiver/receiver_99.csv
because the text is blank.

[DevElCuy]

If you are willing to help, please analyze https://github.com/devcoin/core/blob/master/src/receiver.h#L160 and https://github.com/devcoin/core/blob/master/src/main.cpp

[DevElCuy]

I figured out the fix faster than expected, so we don't need a big reward. Still, we have to test the fix extensively and release a new version of Devcoin! For that reason I change the bounty to 10M DVC from the DevFund to be distributed among all the people that work on fixing this issue. The tester assigned is @cpsilent, which should certify the fix.