Re: Please help verify signature within Dockerfile

2025-02-02 Thread Josef Wolf
Although I got a solution for the initial problem to use gpgv, I am still curious why all the other methods fail. Any ideas? On Fri, Jan 31, 2025 at 12:15:18AM +0100, Josef Wolf wrote: > Hello all, > > I am trying to verify signature of downloaded files when creating a docker > con

Re: Please help verify signature within Dockerfile

2025-01-31 Thread Josef Wolf
On Fri, Jan 31, 2025 at 09:57:24AM +, Andrew Gallagher wrote: > On 30 Jan 2025, at 23:15, Josef Wolf wrote: > > > > I am trying to verify signature of downloaded files when creating a docker > > container. This is what I am trying to do within the Dockerfile: > >

Please help verify signature within Dockerfile

2025-01-30 Thread Josef Wolf
N gpg --verify --trust-model always ql/quicklisp.lisp.asc ql/quicklisp.lisp": while running runtime: exit status 2 BTW: I create an empty ~/.gnupg directory before the very first gpg invocation to prevent use-keyboxd option to be set. Does it really need to be that hard to verify signature wi

Re: WARNING: unsafe ownership on homedir `/m/a/etc/naclient/ppcbackup

2008-05-28 Thread Josef Wolf
On Sat, May 24, 2008 at 02:13:17AM +0200, Josef Wolf wrote: > I am wondering what this error message > >WARNING: unsafe ownership on homedir `/usr/local/etc/backup' > > is trying to tell me. > > This directory is owned by root:myself and has mode 750. So it is &

WARNING: unsafe ownership on homedir `/m/a/etc/naclient/ppcbackup

2008-05-23 Thread Josef Wolf
Hello, I am wondering what this error message WARNING: unsafe ownership on homedir `/usr/local/etc/backup' is trying to tell me. This directory is owned by root:myself and has mode 750. So it is writable only by root and readable only by myself and by root. AFAICS, it is as safe as it can g

Re: Need non-writable --homedir

2006-09-13 Thread Josef Wolf
s, chances are that you keep answering the wrong questions. (just kidding :) > Josef Wolf wrote: > >>> Don't most unices have /dev/random nowadays? I never planned to > >>> run this thing on a windows box :) > >> > >> GnuPG has been ported to many p

Re: Need non-writable --homedir

2006-09-12 Thread Josef Wolf
On Tue, Sep 12, 2006 at 03:05:08PM -0400, David Shaw wrote: > On Tue, Sep 12, 2006 at 08:42:39PM +0200, Josef Wolf wrote: > > > AFAIK, having random_seed be accessible to unauthorized people is > > not acceptable. Thus I have no choice, I just _have_ to use the > > --no

Re: Need non-writable --homedir

2006-09-12 Thread Josef Wolf
On Mon, Sep 11, 2006 at 05:28:25PM -0500, Robert J. Hansen wrote: > Josef Wolf wrote: > > Don't most unices have /dev/random nowadays? I never planned to run > > this thing on a windows box :) > GnuPG has been ported to many platforms. BeOS, OpenVMS, Win32, and many &

Re: Need non-writable --homedir

2006-09-11 Thread Josef Wolf
On Mon, Sep 11, 2006 at 03:27:59PM -0500, Robert J. Hansen wrote: > Josef Wolf wrote: > 1. /dev/random isn't available on all platforms. GnuPG's random number > generator is. Don't most unices have /dev/random nowadays? I never planned to run this thing on a wi

Re: Need non-writable --homedir

2006-09-11 Thread Josef Wolf
Thanks for your response, Robert! On Sun, Sep 10, 2006 at 05:36:33PM -0500, Robert J. Hansen wrote: > Josef Wolf wrote: > > 1. It locks the keyring. --lock-never will avoid this. Is it safe > > to use --lock-never as long as it is guaranteed that _only_ "gpg -e"

Need non-writable --homedir

2006-09-10 Thread Josef Wolf
Hello! I need a setup where the user running "gpg -e -r foobar" is not able to modify keyring contents. I tried: # chown -R root:user ~user/.gnupg # chmod -R o=rwX,g=rX,o= ~user/.gnupg Unfortunately, this don't work because gpg does some write operations in its .gnupg directory: 1. It

Need non-writable --homedir

2006-09-10 Thread Josef Wolf
Hello! I need a setup where the user running "gpg -e -r foobar" is not able to modify keyring contents. I tried: # chown -R root:user ~user/.gnupg # chmod -R o=rwX,g=rX,o= ~user/.gnupg Unfortunately, this don't work because gpg does some write operations in its .gnupg directory: 1. It