Re: signify: invalid comment in SHA256
On Sat, Jun 17, 2023 at 10:33:01PM -0700, Philip Guenther wrote: > On Sat, Jun 17, 2023 at 9:38???PM Avon Robertson wrote: > > > Used lynx to get the 4 files shown below. The shell prompt is a 2 > > line prompt with current dir on 1st line,'$ ' only, on the 2nd line. > > > > Below is output captured from a tmux pane with a script. > > > > aahno:/ > > $ cat /etc/installurl > > https://mirror.aarnet.edu.au/pub/OpenBSD > > aahno:/ > > $ lynx $(cat /etc/installurl)/snapshots/amd64 > > aahno:/ > > $ cd ~/download > > aahno:/home/anon/download > > $ ls -la > > total 1361400 > > drwxr-x--- 2 anon anon512 Jun 18 15:35 . > > drwxr-xr-x 25 anon anon 1536 Jun 18 08:01 .. > > -rw-r- 1 anon anon 44817 Jun 18 15:34 INSTALL.amd64 > > -rw-r- 1 anon anon 1992 Jun 18 15:34 SHA256 > > -rw-r- 1 anon anon 2144 Jun 18 15:34 SHA256.sig > > -rw-r- 1 anon anon 696745984 Jun 18 15:36 install73.img > > aahno:/home/anon/download > > $ signify -C -p /etc/signify/openbsd-73-base.pub -x SHA256 install73.img > > signify: invalid comment in SHA256; must start with 'untrusted comment: ' > > aahno:/home/anon/download > > > You downloaded SHA256.sig, but then told signify to read the SHA256 file. > Perhaps you should follow all the examples for signify and pass it the > SHA256.sig file. > > > Philip Guenther What a dummy I am Philip. I was reading the example in INSTALL.amd64 as I entered the command too. Thank you for your reply.
Re: signify: invalid comment in SHA256
On Sat, Jun 17, 2023 at 9:38 PM Avon Robertson wrote: > Used lynx to get the 4 files shown below. The shell prompt is a 2 > line prompt with current dir on 1st line,'$ ' only, on the 2nd line. > > Below is output captured from a tmux pane with a script. > > aahno:/ > $ cat /etc/installurl > https://mirror.aarnet.edu.au/pub/OpenBSD > aahno:/ > $ lynx $(cat /etc/installurl)/snapshots/amd64 > aahno:/ > $ cd ~/download > aahno:/home/anon/download > $ ls -la > total 1361400 > drwxr-x--- 2 anon anon512 Jun 18 15:35 . > drwxr-xr-x 25 anon anon 1536 Jun 18 08:01 .. > -rw-r- 1 anon anon 44817 Jun 18 15:34 INSTALL.amd64 > -rw-r- 1 anon anon 1992 Jun 18 15:34 SHA256 > -rw-r- 1 anon anon 2144 Jun 18 15:34 SHA256.sig > -rw-r- 1 anon anon 696745984 Jun 18 15:36 install73.img > aahno:/home/anon/download > $ signify -C -p /etc/signify/openbsd-73-base.pub -x SHA256 install73.img > signify: invalid comment in SHA256; must start with 'untrusted comment: ' > aahno:/home/anon/download You downloaded SHA256.sig, but then told signify to read the SHA256 file. Perhaps you should follow all the examples for signify and pass it the SHA256.sig file. Philip Guenther
signify: invalid comment in SHA256
Hello, Used lynx to get the 4 files shown below. The shell prompt is a 2 line prompt with current dir on 1st line,'$ ' only, on the 2nd line. Below is output captured from a tmux pane with a script. aahno:/ $ cat /etc/installurl https://mirror.aarnet.edu.au/pub/OpenBSD aahno:/ $ lynx $(cat /etc/installurl)/snapshots/amd64 aahno:/ $ cd ~/download aahno:/home/anon/download $ ls -la total 1361400 drwxr-x--- 2 anon anon512 Jun 18 15:35 . drwxr-xr-x 25 anon anon 1536 Jun 18 08:01 .. -rw-r- 1 anon anon 44817 Jun 18 15:34 INSTALL.amd64 -rw-r- 1 anon anon 1992 Jun 18 15:34 SHA256 -rw-r- 1 anon anon 2144 Jun 18 15:34 SHA256.sig -rw-r- 1 anon anon 696745984 Jun 18 15:36 install73.img aahno:/home/anon/download $ signify -C -p /etc/signify/openbsd-73-base.pub -x SHA256 install73.img signify: invalid comment in SHA256; must start with 'untrusted comment: ' aahno:/home/anon/download $ gtmuxpane /home/anon/mailinc/signify-invalid-comment.txt Is the above 'untrusted comment: ' a stopper for installing with this install73.img. Advice will be very appreciated.
