Bitcoin Forum
May 08, 2024, 11:03:07 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: I created a tutorial about how to check PGP signatures on Linux.  (Read 111 times)
Rayser (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 2


View Profile
February 24, 2019, 10:37:17 AM
 #1

https://github.com/spesmilo/electrum-docs/blob/16ee910d16f67b58efd66943d7d0b4c35d3562e4/e.g.%20gpg-check.rst
1715209387
Hero Member
*
Offline Offline

Posts: 1715209387

View Profile Personal Message (Offline)

Ignore
1715209387
Reply with quote  #2

1715209387
Report to moderator
1715209387
Hero Member
*
Offline Offline

Posts: 1715209387

View Profile Personal Message (Offline)

Ignore
1715209387
Reply with quote  #2

1715209387
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715209387
Hero Member
*
Offline Offline

Posts: 1715209387

View Profile Personal Message (Offline)

Ignore
1715209387
Reply with quote  #2

1715209387
Report to moderator
1715209387
Hero Member
*
Offline Offline

Posts: 1715209387

View Profile Personal Message (Offline)

Ignore
1715209387
Reply with quote  #2

1715209387
Report to moderator
1715209387
Hero Member
*
Offline Offline

Posts: 1715209387

View Profile Personal Message (Offline)

Ignore
1715209387
Reply with quote  #2

1715209387
Report to moderator
pooya87
Legendary
*
Offline Offline

Activity: 3444
Merit: 10555



View Profile
February 25, 2019, 04:05:21 AM
 #2

this is very vague and incomplete in my opinion which is probably why it has not been merged yet.

i suggest turning it into clear steps and then also include alternative ways and also possible different replies that you get from each command.
for example:
1. Download files from electrum.org
-this should include what files (the .exe or tarball or .dmg file,... + signature file)
2. get the developer's public key
- then it should mention the alternative way here also you must mention what to do when you fail to connect to mit server since it is a common thing for it to go down!
3. do the verification
this should include the example of BOTH good and bad signatures highlighting the part of the response message saying whether it was good or bad and also explaining the other part (the error) that always confuses everyone.

.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
Rayser (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 2


View Profile
February 25, 2019, 12:47:48 PM
 #3

this is very vague and incomplete in my opinion which is probably why it has not been merged yet.

i suggest turning it into clear steps and then also include alternative ways and also possible different replies that you get from each command.
for example:
1. Download files from electrum.org
-this should include what files (the .exe or tarball or .dmg file,... + signature file)
2. get the developer's public key
- then it should mention the alternative way here also you must mention what to do when you fail to connect to mit server since it is a common thing for it to go down!
3. do the verification
this should include the example of BOTH good and bad signatures highlighting the part of the response message saying whether it was good or bad and also explaining the other part (the error) that always confuses everyone.

Wanna help?
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!