> To keep it neat, let's say both files are in /data/bsd-stuff, so we
> have:
> /data/bsd-stuff/install62.iso
> /data/bsd-stuff/SHA256.sig
where did you download the public key?
On 02/09/18 17:22, Philip Mundhenk wrote:
Thank you both. That worked. Ubuntu already had a package named signify so,
with all 3 files in the $PWD, the correct command is:
signify-openbsd -C -p openbsd-62-base.pub -x SHA256.sig install62.iso
Possibly part of the problem is that the Ubuntu pa
Thank you both. That worked. Ubuntu already had a package named signify so,
with all 3 files in the $PWD, the correct command is:
signify-openbsd -C -p openbsd-62-base.pub -x SHA256.sig install62.iso
Possibly part of the problem is that the Ubuntu package signify-openbsd-keys
does NOT put anyth
On Fri 09 Feb 2018 5:50 PM, Kenneth Gober wrote:
>
> This paper provides some good background about why signify rather than
> https or gpg:
>
> http://www.openbsd.org/papers/bsdcan-signify.html
And the video:
https://www.youtube.com/watch?v=9R5s3l-0wh0
It's quite creative to include the next s
On Fri, Feb 9, 2018 at 4:44 PM, Kevin Chadwick wrote:
> On Fri, 09 Feb 2018 16:11:01 -0500
>> but I can't for the life of me figure out how to cryptographically
>> verify the legitimacy of install62.iso with SHA256.sig.
>
> I've never done it on linux however try
>
> signify -C -p /etc/signify/ope
On Fri, 09 Feb 2018 16:11:01 -0500
> but I can't for the life of me figure out how to cryptographically
> verify the legitimacy of install62.iso with SHA256.sig.
I've never done it on linux however try
signify -C -p /etc/signify/openbsd-62-base.pub -x SHA256.sig
https://man.openbsd.org/signify
I've installed:
signify-openbsd
signify-openbsd-keys
in an ultra-light (think Lubuntu on Atkins & amphetimines) Ubuntu 16.04.
I guess I'm just a dumb Ubuntard, despite my Intertel membership, but I can't
for the life of me figure out how to cryptographically verify the legitimacy of
install62.
7 matches
Mail list logo
