-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 8267fc6bcde0581f13abb82fba275a70001a6044e9fb82e54b921d192a468ca3 udevil-0.2.2.tar.xz 6c9484ecdcc4e6823a5796faa56eee2b99b5c1daa870be119797e063d3b805e6 udevil-0.2.2-installer.sh f0a38132016b24d905f8d8037ec0fa2b962c2dffaea46b0d7f0af29aec7b6523 udevil_0.2.2-1_all.deb # # This file (udevil-0.2.2.SHA256.asc) is used to authenticate download of # udevil version 0.2.2 # # Homepage: http://ignorantguru.github.com/udevil/ # # # Why Authenticate? # # Verifying the authenticity of downloaded files prior to installation is # important to ensure that your download is not corrupt and that no one has # tampered with the server holding the files. # # # 1) If you don't already have IgnorantGuru's CURRENT key on your keyring: # # gpg --keyserver keys.gnupg.net --recv-keys 0x7977070A723C6CCB696C0B0227A5AC5A01937621 # (if you receive an error, try again) # # Also visually verify that the given fingerprint matches the one shown here: # http://igurublog.wordpress.com/contact-ignorantguru/ # # # 2) Download one or more files (the first is required): # # wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.2/udevil-0.2.2.SHA256.asc # wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.2/udevil-0.2.2.tar.xz # wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.2/udevil-0.2.2-installer.sh # wget https://raw.github.com/IgnorantGuru/udevil/master/packages/0.2.2/udevil_0.2.2-1_all.deb # # # 3) Check signature and files: # # gpg -d udevil-0.2.2.SHA256.asc | sha256sum --check # # This should report a good signature and an OK for each file present: # # gpg: Signature made using DSA key ID 01937621 <-- # --> udevil-0.2.2.tar.xz: OK # --> udevil-0.2.2-installer.sh: OK # --> udevil_0.2.2-1_all.deb: OK # --> gpg: Good signature from IgnorantGuru # gpg: WARNING: This key is not certified with a trusted signature! # gpg: There is no indication that the signature belongs to the owner. # sha256sum: WARNING: x lines are improperly formatted # # If "BAD signature" or the wrong key ID is reported, or if FAILED appears # next to any file you plan to use, DO NOT USE the file. A "key is not # certified" warning (shown above) is normal and can be safely ignored if # you visually verified the key fingerprint in step 1. # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iF4EAREIAAYFAk/BC+wACgkQJ6WsWgGTdiFknQEAp6jV4YhthHV4GC+XDVhwabYC JwbOXUPtwmtaPemac00A/jCA5IaQW7/sEc3n0Wo4R49H23z64cCSL8NQKRjfskGw =OUZX -----END PGP SIGNATURE-----