Re: ftp down

2024-08-23 Thread Andreas Metzler
On 2024-08-22 Alex via Gnupg-users  wrote:
[...]
> In case ftp is something which should be still provided maybe twoftpd could
> be an option.

> https://packages.debian.org/buster/twoftpd
> http://www.untroubled.org/twoftpd/
[...]

Hello,

Sure, a package removed from Debian about two years ago because of
"unmaintained, dead upstream, plenty of alternatives".

I do not get the whole discussion, surely Werner's and his collagues'
time can spent more productively than managing an ftp server? The
protocol really is not very popular anymore and if one really needs to
use it most mirrors still offer ftp.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: baffled at "Chapter 1. Getting Started" due to gpg: agent_genkey failed: No pinentry

2024-07-20 Thread Andreas Metzler
On 2024-07-20 Dennis Clarke via Gnupg-users  wrote:
> Looking at https://www.gnupg.org/gph/en/manual/c14.html one would get
> the idea that GPG would "just work" given that pinentry is right there

> oberon$ which pinentry
> /usr/local/bin/pinentry
[...]

Hello,

afaik gnupg does not search for the helpers on PATH, their location is
built into the binary, running gpgconf should show where it is looking.

cu Andreas

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: 2.2.43 and vsd-allow-ocb

2024-05-06 Thread Andreas Metzler
On 2024-05-06 Werner Koch  wrote:
> On Sat,  4 May 2024 18:45, Andreas Metzler said:

> > rG0a355b2fe7d8 gpg: Add compatibility flag "vsd-allow-ocb"
> > rGa545e14e8a74 gpg: Support OCB encryption.

> > Which understand to mean that 2.2.43 would by default both generate keys
> > with 'AEAD: OCB' and use OCB when encrypting to keys with that flag set.
> > And this behavior could have been disabled with '--compatibility-flags

> No misunderstood this.  OCB encryption is indeed supported regardless of
> the compatibiliy flag.

> What the compatibility flag does is to allow OCB also in
> --compliance=de-vs mode.
[...]

Hello Werner,
So in my test  (without --compliance=de-vs) 2.2.43 /should/ have
automatically used OCB when encrypting for a key which has 'AEAD: OCB'
set?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


2.2.43 and vsd-allow-ocb

2024-05-04 Thread Andreas Metzler
Hello,

2.2.42`s NEWS said
  * gpg: Support OCB encryption.  [T6263]

and https://dev.gnupg.org/T6263 shows two commits
rG0a355b2fe7d8 gpg: Add compatibility flag "vsd-allow-ocb"
rGa545e14e8a74 gpg: Support OCB encryption.

The commit message for 0a355b2fe7d8 said
| * g10/gpg.c (compatibility_flags): Add "vsd-allow-ocb".
| (main): And set it.

Which understand to mean that 2.2.43 would by default both generate keys
with 'AEAD: OCB' and use OCB when encrypting to keys with that flag set.
And this behavior could have been disabled with '--compatibility-flags
none'.

However afaict (gpg --compatibility-flags ?) the flag is not set by
default and indeed --quick-generate-key without --compatibility-flags
vsd-allow-ocb generates a key without "AEAD: OCB" and does not use OCB
for encrypting to a key with "AEAD: OCB" set.

Is my understanding flawed?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Fwd: speedo.mk errors out

2024-03-23 Thread Andreas Metzler
On 2024-03-22 Christian Sommer via Gnupg-users  wrote:
> hi.
> building GnuPG by speedo.mk on current master branch fails. The log
> attached for building the dependencies looks fine. 
[...]

Good morning,

Does not look "fine" to me:

configure:9456: Use gpgrt-config as libassuan-config
configure:9519: checking for LIBASSUAN - version >= 3.0.0
configure:9566: result: no
[...]
*** You need libassuan to build this program.
*** This library is for example available at
***   https://gnupg.org/ftp/gcrypt/libassuan/
*** (at least version 3.0.0 (API 3) is required).

AFAIUI gnupg master requires libassuan 3 which has not yet been released.

cu andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users