Feature #7664
Add back the SHA256 checksum somewhere
100%
Description
Since we removed the instructions for ISO verification using Firefox,
the SHA256 checksum of our ISO image is not linked anymore on the
website. I’ve been sending the link maybe 4-5 times in a week, so people
are actually using it (without instructions).
It would be good to have it back in the documentation somewhere.
Maybe straight into https://tails.boum.org/download/#download in the
space below “Cryptographic signature”. People who know what to do with
it will find it easily.
Any opinion on that?
Files
Subtasks
History
#1 Updated by intrigeri 2014-07-26 08:35:55
> I’ve been sending the link maybe 4-5 times in a week, so people are
> actually using it (without instructions).
Just curious: do we know why they’re using it, as opposed to doing the OpenPGP signature verification (without checking the signing key properly), that is equivalent? (What I have in mind is that perhaps re-adding the hash is only hiding another problem in how this documentation is presented. Anyway, I have no strong feelings about it. Your call! :)
#2 Updated by sajolida 2014-07-26 09:24:30
> Just curious: do we know why they’re using it, as opposed to doing
> the OpenPGP signature verification (without checking the signing key
> properly), that is equivalent? (What I have in mind is that perhaps
> re-adding the hash is only hiding another problem in how this
> documentation is presented. Anyway, I have no strong feelings about
> it. Your call! :)
I didn’t ask them, I’ll do that next time I need to send that link.
My hypothesis is that they followed their path of least effort. Those
people probably already know how to verify checksums themselves without
Firefox, but they didn’t knew the OpenPGP techniques. Checksum
verification is still quite more common to verify software that OpenPGP
signatures.
As we proposed the checksum in the past, they were used to doing that
and are now reclaiming back that info.
#3 Updated by BitingBird 2014-07-26 23:27:36
I think that’s a good idea.
#4 Updated by sajolida 2014-08-06 13:15:18
- Target version set to Tails_1.1.1
#5 Updated by sajolida 2014-08-06 18:02:46
- Category set to Installation
- Assignee deleted (
sajolida) - QA Check set to Ready for QA
- Feature Branch set to web/7664-add-back-checksum
- Type of work changed from Documentation to Website
As expected, this thing is used by people who already know how to verify the checksum but don’t know how to do OpenPGP.
#6 Updated by intrigeri 2014-08-08 13:38:05
- Assignee set to intrigeri
#7 Updated by intrigeri 2014-08-08 13:43:58
- Status changed from Confirmed to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 0 to 100
- QA Check changed from Ready for QA to Pass
Merged into master.
#8 Updated by BitingBird 2014-08-08 17:10:40
On my screen, the checksum goes accross the second part of the page. It’s a bit ugly, but not dramatic.
#9 Updated by sajolida 2014-08-08 19:37:29
- Status changed from Resolved to In Progress
- QA Check changed from Pass to Dev Needed
Oops, too bad! Which browser and which version? Mind sending a screenshot?
#10 Updated by sajolida 2014-08-08 19:37:45
- Assignee set to BitingBird
- QA Check changed from Dev Needed to Info Needed
#11 Updated by BitingBird 2014-08-08 20:30:54
- File screenshot.png added
#12 Updated by BitingBird 2014-08-08 20:31:10
- Assignee changed from BitingBird to sajolida
- QA Check deleted (
Info Needed)
#13 Updated by BitingBird 2014-08-08 20:32:15
Iceweasel 30.0
#14 Updated by sajolida 2014-08-08 21:10:53
This is very weird because I tested it with three different Iceweasel 30 (local, TBB, and Tails) and GNOME Web , and got the checksum rewapped fine :(
Maybe you didn’t get the new version of the local.css file. Could you try to restart your browser maybe?
#15 Updated by BitingBird 2014-08-09 14:47:48
- Status changed from In Progress to Resolved
Right, today it works, sorry :/
#16 Updated by sajolida 2014-08-10 11:13:28
- Assignee deleted (
sajolida)