> On May 12, 2025, at 9:27 AM, Werner Koch wrote:
>
> On Sun, 11 May 2025 12:08, Nick said:
>
>> Is it because --list-keys shows 0 for signed keys?
>> gpgsm: can't sign using 'em...@gmail.com <mailto:em...@gmail.com>': No
>> public key
>
an't sign using 'em...@gmail.com <mailto:em...@gmail.com>': No
> public key
The error message might be confusing, as it should show "no secret key"
but in your case it seems that you don't vene have the public key for
"em...@gmail.com".
BTW, having
I can’t sign using my public key which --list-keys shows. Does anyone have
a solution or pointers on how to debug this further?
Is it because --list-keys shows 0 for signed keys?
$ echo "signme" |gpgsm -s -u email@gmail.comgpgsm: can't sign using
'em...@gmail.com': No
Please refrain from html emails on the listserv Am 11.05.2025 um 18:14 schrieb Nick via Gnupg-users :I can’t sign using my public key which --list-keys shows. Does anyone have a solution or pointers on how to debug this further?Is it because --list-keys shows 0 for signed keys?$ echo "s
I can’t sign using my public key which --list-keys shows. Does anyone have a
solution or pointers on how to debug this further?
Is it because --list-keys shows 0 for signed keys?
$ echo "signme" |gpgsm -s -u em...@gmail.com <mailto:em...@gmail.com>
gpgsm: can't sign u
On Wed, 17 Jan 2024 08:22, Thomas said:
> I didn't use ssh @ on purpose because I'm used to
> use the same user on remoteserver as on client.
Common problem for me too when I ssh into a Windows box where I use a
different user name on purpose ;-). This way you don't accidently login
into a testb
Hello,
accidently I identified the root cause for this issue.
I executed this SSH command:
ssh
I didn't use ssh @ on purpose because I'm used to
use the same user on remoteserver as on client.
After executing SSH command
ssh @
gpg-agent works as expected and I can login with
d it
on my testbox (Windows 10.0 build 19045) using my regular token:
debug1: Next authentication method: publickey
debug1: Offering public key: cardno:FFFE_xxx ED25519
SHA256:tXYM7ne2kI+ZUw7jGii9LBhoz8uB0ucKv28OSSW6a/g agent
debug1: Server accepts key: cardno:FFFE_xx
Hello Werner,
thanks for your reply.
Your understanding is correct:
From Win 11 to any other (Linux) server using SSH.
Actually I installed PuTTY only because of this statement (I found in my
research):
"[...] The ssh-pageant provides the same kind of functionality to ssh
but, as opposed to s
Hi!
I am not 100% sure whether I did understand you correctly:
You are in Windows 11 and want to use its native OpenSSH client to
connect to some other ssh server.
Why do you need Putty, which has an integrated but different ssh
implementation?
For Putty you had *enable-putty-support* in your g
Hello,
in the past I used
Windows 10
+ Smartcard
+ MobaXterm
for SSH public key authentication w/o problems incl. SSH forward.
Now I have a new device with Windows 11, and I want to use the same
Smartcard for SSH public key authentication using Win 11 (native) SSH
client.
Therfore I
On Fri, Jan 5, 2024 at 2:43 PM Werner Koch wrote:
> That is right. The ssh-agent protocol has no means to tell the
> ssh-agent or gpg-agent some important environment cariabales, like the
> current tty or DISPLAY.
Interesting, thanks for the look behind the scenes!
> I am so used to run the upd
On Fri, 5 Jan 2024 10:07, Felix E. Klee said:
>> gpg-connect-agent updatestartuptty /bye
>
> or otherwise, I get no PIN entry dialog / prompt
That is right. The ssh-agent protocol has no means to tell the
ssh-agent or gpg-agent some important environment cariabales, like the
current tty or
On Fri, Nov 24, 2023 at 9:09 AM Felix E. Klee wrote:
> In addition, I need:
>
> gpg-connect-agent updatestartuptty /bye
or otherwise, I get no PIN entry dialog / prompt
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mail
Thanks, Ingo!
Looking at my log, I realize that I indeed uploaded the primary key when
I did `keytocard`. I did not do `key 2` to select the authentication sub
key. Instead I was assuming that GnuPG does automatically select the
right sub key. There was a warning about moving the primary key, whic
Thanks, Ingo!
Looking at my log, I realize that I indeed uploaded the primary key when
I did `keytocard`. I did not do `key 2` to select the authentication sub
key. Instead I was assuming that GnuPG does automatically select the
right sub key. There was a warning about moving the primary key, whic
On Mittwoch, 27. Dezember 2023 13:40:40 CET Felix E. Klee wrote:
> Thanks for pointing out that the signature key and the authentication
> keys are identical:
>
> $ gpg --card-status
[...]
> Authentication key: 7A0F E73D DB74 4F0F 9734 1DA7 1BE3 49D1 1B6E
> D589
> created ..
Thanks for pointing out that the signature key and the authentication
keys are identical:
$ gpg --card-status
[…]
Signature key : 7A0F E73D DB74 4F0F 9734 1DA7 1BE3 49D1 1B6E
D589
created : 2023-06-29 03:50:43
Encryption key: DBBD 3239 D0F1 4326 808D FC8
Thanks for pointing out that the signature key and the authentication
keys are identical:
$ gpg --card-status
[…]
Signature key : 7A0F E73D DB74 4F0F 9734 1DA7 1BE3 49D1 1B6E
D589
created : 2023-06-29 03:50:43
Encryption key: DBBD 3239 D0F1 4326 808D FC8
On Mittwoch, 29. November 2023 03:52:36 CET Felix E. Klee wrote:
> So `gpg --card-status` imports [SC] and [E], but not [A]:
>
> $ rm ~/.gnupg/private-keys-v1.d/*
> $ ls -a1 ~/.gnupg/private-keys-v1.d/
> .
> ..
> $ gpg --card-status
> […]
> Signature key : 7A0F E73D
To my knowledge, no (explicit) agent forwarding is required for
ProxyJump configurations.
I am using the following configuration to access a LAN machine over the
Internet. Both machines use the GnuPG key for authentication.
Host rdeep
HostName 192.168.1.151
ProxyJump verbuecheln.ch
Id
gs of MobaXterm I enabled SSH forwarding.
As of now I don't want to continue using MobaXterm on Windows 11, but
using Windows Terminal.
I can run ssh-add.exe -L in Windows PowerShell and get the correct SSH
public key fetched from secure card.
If you are using a Windows port of OpenSSH, try &
So `gpg --card-status` imports [SC] and [E], but not [A]:
$ rm ~/.gnupg/private-keys-v1.d/*
$ ls -a1 ~/.gnupg/private-keys-v1.d/
.
..
$ gpg --card-status
[…]
Signature key : 7A0F E73D DB74 4F0F 9734 1DA7 1BE3 49D1 1B6E
D589
created : 2023-06-29 03
On Thu, Nov 23, 2023 at 10:17 AM Felix E. Klee
wrote:
> Can you explain why the output of `ssh-add -L` did not change? Also
> why is it not the same as the output from `gpg --export-ssh-key
> yubi...@f76.eu`?
OK, I may have found the issue:
$ grep -rl Use-for-ssh ~/.gnupg/private-keys-v1.d/*
erm I enabled SSH forwarding.
As of now I don't want to continue using MobaXterm on Windows 11, but
using Windows Terminal.
I can run ssh-add.exe -L in Windows PowerShell and get the correct SSH
public key fetched from secure card.
THX
Am 28.11.23 um 03:53 schrieb Jacob Bachmeyer:
Thomas
Thomas via Gnupg-users wrote:
Hello Stephan,
thanks for your reply.
When you say I should modify ~/.ssh/config, where is this file?
On jumphost?
You need to configure SSH agent forwarding on your client, which will
provide access to your local SSH agent at the jumphost via the SSH
connec
werShell and get the correct SSH
public key fetched from secure card.
But once connected to jumphost, all SSH relevant information is
unavailable.
THX
On 2023-11-25 12:30, Stephan Verbücheln via Gnupg-users wrote:
Coincidentally, I have a similar setup. Fortunately, you do *not* need
On 25.11.23 13:24, Thomas Schneider via Gnupg-users wrote:
> Hello Stephan,
>
> thanks for your reply.
>
> When you say I should modify ~/.ssh/config, where is this file?
> On jumphost?
>
> Actually I have a working setup on Windows 10, but here I use another
> terminal emulator: MobaXterm.
> An
Hello Stephan,
thanks for your reply.
When you say I should modify ~/.ssh/config, where is this file?
On jumphost?
Actually I have a working setup on Windows 10, but here I use another
terminal emulator: MobaXterm.
And in the settings of MobaXterm I enabled SSH forwarding.
As of now I don't
Hello Stephan,
thanks for your reply.
When you say I should modify ~/.ssh/config, where is this file?
On jumphost?
Actually I have a working setup on Windows 10, but here I use another
terminal emulator: MobaXterm.
And in the settings of MobaXterm I enabled SSH forwarding.
As of now I don't
Coincidentally, I have a similar setup. Fortunately, you do *not* need
Agent Forwarding for authentication via jump hosts.
The entry for your host (in “~/.ssh/config”) for this host should look
something like this:
Host myalias
HostName myserver.com
ProxyJump jumpserver.net
IdentityAg
previously set on
Nitrokey.
After this I'm connected to the jumphost (Linux).
Now I want to connect to the server using command ssh ,
however I need to enter a password.
This means public key authentication fails.
And I think this fails because SSH agent forwarding is not working.
Can y
On Thu, Nov 23, 2023 at 2:19 PM Stephan Verbücheln via Gnupg-users
wrote:
> Host gitlab.com
> HostName gitlab.com
> User git
> IdentityAgent ${XDG_RUNTIME_DIR}/gnupg/S.gpg-agent.ssh
Thanks, that works. Even the variable is expanded.
In addition, I need:
gpg-connect-agent updates
Another convenient way is to use “~/.config/ssh”. This allows different
configurations per host without changing your global environment.
Example:
Host gitlab.com
HostName gitlab.com
User git
IdentityAgent ${XDG_RUNTIME_DIR}/gnupg/S.gpg-agent.ssh
Regards
Stephan
signature.asc
Descr
On Wed, Nov 22, 2023 at 8:57 PM Werner Koch wrote:
> Here is the snippet from by ~/.bashrc
I have a similar config. Thank you for the detailed explanation!
Only the following line does not work right after autologin (default
with Ubuntu / WSL2), seems like something is not ready yet.
gpg-co
On Tue, Nov 21, 2023 at 12:38 AM Ingo Klöcker wrote:
> $ gpg --export-ssh-key 1B6ED589
Thanks, this worked! I then added the key on the remote system to:
~/.ssh/authorized_keys
However, I could not log in. SSH reports:
Permission denied (publickey).
I then tried exporting the key usi
On Wed, 22 Nov 2023 19:39, Felix E. Klee said:
> However, I could not log in. SSH reports:
>
> Permission denied (publickey).
You need to make sure that the gpg-agent is running and the
SSH_AUTH_SOCK envvar is set correctly. Here is the snippet from by
~/.bashrc
--8<---cut here
On Tue, Nov 21, 2023 at 12:38 AM Ingo Klöcker wrote:
> $ gpg --export-ssh-key 1B6ED589
Thanks, this worked! I then added the key on the remote system to:
~/.ssh/authorized_keys
However, I could not log in. SSH reports:
Permission denied (publickey).
I then tried exporting the key usi
sub rsa4096/D2E31736 2023-06-29 [E]
> sub rsa4096/FBA5B1E5 2023-11-20 [A]
>
> $ gpg --export-ssh-key FBA5B1E5
> gpg: key "FBA5B1E5" not found: Unusable public key
> gpg: export as ssh key failed: Unusable public key
Try
$ gpg --export-ssh-key FBA5B1E5!
(n
[E]
sub rsa4096/FBA5B1E5 2023-11-20 [A]
$ gpg --export-ssh-key FBA5B1E5
gpg: key "FBA5B1E5" not found: Unusable public key
gpg: export as ssh key failed: Unusable public key
GnuPG version:
$ gpg --version
gpg (GnuPG) 2.2.27
libgcrypt 1.9.4
Copyright (C) 2021
Hi, Guillermo.
You don’t say what sort of keys these are. V4? V5? Elliptic curve? Some recent
kinds of keys may not be compatible with SKS. Have you compared with hockeypuck
to see if it serves them any differently?
Thanks,
Andrew.
> On 12 May 2023, at 21:08, Guillermo Montoya Naranjo via Gnup
Good afternoon, I have an sks server installed, which synchronizes with
kleopatra, I create a pair of openPGPG keys, which I then publish to the
sks server and it does it successfully, but when I execute the search
option, it throws me the following error, as shown in the image
gpg: no valid OpenP
On Mon, Apr 17, 2023 at 03:22:42PM +0200, Werner Koch via Gnupg-users wrote:
> >> > gpg (GnuPG) 2.0.22
>
> That version reached end-of-life more than 5 years ago. Don't use it.
If you need a newer version of GnuPG for RHEL7 systems, you can install
gnupg24-static from this COPR:
https://copr.fe
On Sun, 16 Apr 2023 10:12, Mike Schleif said:
>> > gpg (GnuPG) 2.0.22
That version reached end-of-life more than 5 years ago. Don't use it.
>> $ gpg --version --no-copyright
--no-copyright - There is no such option. What you meant was
--no-greeting.
Salam-Shalom,
Werner
--
The pio
Mike Schleif wrote:
> Yes, I see that.
>
> However, our public key was generated by our GPG; and this file is
> encrypted with our public key, since there is NO missing "secret key" error.
>
> Why, then, the subject error message?
Perhaps the file is signed by an
Yes, I see that.
However, our public key was generated by our GPG; and this file is
encrypted with our public key, since there is NO missing "secret key" error.
Why, then, the subject error message?
On Sat, Apr 15, 2023 at 3:37 PM Todd Zullinger via Gnupg-users <
gnupg-users@gnu
Mike Schleif wrote:
> $ gpg --version
> gpg (GnuPG) 2.0.22
> libgcrypt 1.5.3
>
> $ cat /etc/system-release
> CentOS Linux release 7.9.2009 (Core)
Algorithm 18 is ECDH, which is not supported by gpg on
CentOS 7. You can confirm this in the Pubkey line of the
gpg --version output:
$ gpg --versi
On Sat, Apr 15, 2023 at 11:17:31AM -0500, Mike Schleif wrote:
> On trying to decrypt a file, we get the subject error on failure.
What version of GnuPG are you using? Running on what platform?
Bruce
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
ht
$ gpg --version
gpg (GnuPG) 2.0.22
libgcrypt 1.5.3
$ cat /etc/system-release
CentOS Linux release 7.9.2009 (Core)
On Sat, Apr 15, 2023 at 1:36 PM Bruce Walzer wrote:
> On Sat, Apr 15, 2023 at 11:17:31AM -0500, Mike Schleif wrote:
> > On trying to decrypt a file, we get the subject error on fai
On trying to decrypt a file, we get the subject error on failure.
What does this mean?
How ought we deal with this?
Please, advise. Thank you.
~ Mike
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-use
WaPo also does have SecureDrop, but I'm not sure how often that gets
used either.
On Tue, Aug 9, 2022 at 10:34 PM Jay Sulzberger via Gnupg-users
wrote:
>
>
> On Sun, 7 Aug 2022, Andrew Gallagher wrote:
>
> >
> >> On 7 Aug 2022, at 17:28, Jay Sulzberger via Gnupg-users
> >> wrote:
> >>
> >> And
Hi,
On Sun, 2023-02-26 at 20:53 +0100, Francesco Ariis wrote:
> Il 26 febbraio 2023 alle 14:09 Richard Bostrom via Gnupg-users ha
> scritto:
> > May I please ask why some 4096 bit keys are longer then others?
> >
> > Richard Stallmans key is much longer then my 4096 bit key.
>
> I suspect: signa
Hello Richard,
Il 26 febbraio 2023 alle 14:09 Richard Bostrom via Gnupg-users ha scritto:
> May I please ask why some 4096 bit keys are longer then others?
>
> Richard Stallmans key is much longer then my 4096 bit key.
I suspect: signatures. They make keys longer
—F
___
Dear sirs and ladies!
May I please ask why some 4096 bit keys are longer then others?
Richard Stallmans key is much longer then my 4096 bit key.
Thank you.
Best regards
Richardh Bostrom
Sent with [Proton Mail](https://proton.me/) secure email.___
Gn
regards,
Joel
Sent from my iPhone
> On 1 Feb 2023, at 10:01, Andrew Gallagher wrote:
>
> On 31 Jan 2023, at 19:52, Joel via Gnupg-users wrote:
>>
>> Hello!
>>
>> I am trying to sign a public key, but I get an error saying, `gpg: signing
>> failed: No secr
On 31 Jan 2023, at 19:52, Joel via Gnupg-users wrote:
>
> Hello!
>
> I am trying to sign a public key, but I get an error saying, `gpg: signing
> failed: No secret key`. However, a normal signing on a file works perfectly
> fine. I suspect it could be something because I hav
Hello!
I am trying to sign a public key, but I get an error saying, `gpg: signing
failed: No secret key`. However, a normal signing on a file works perfectly
fine. I suspect it could be something because I have a yubikey and it might not
work as I initially expected. Have anyone had similar
On Sun, 7 Aug 2022, Andrew Gallagher wrote:
On 7 Aug 2022, at 17:28, Jay Sulzberger via Gnupg-users
wrote:
Andrew, do the sks keyservers work today?
I was able to find the key by going to
https://keyserver.ubuntu.com/
and putting
EC6C2905F0F93C0373946CA10642427A5FF780BE
into the sear
> On 7 Aug 2022, at 19:31, john doe via Gnupg-users
> wrote:
>
> Why did you published the key to the sks key servers?
>
> I guess my question is about the reasoning behind using sks key server
> instead of WKD or Hagrid.
WKD publication can only be done by (or with the cooperation of) the d
Sorry for hijacking the thread but without the context I'm not sure that
my question would have been understandable.
On 8/7/2022 7:59 PM, Andrew Gallagher via Gnupg-users wrote:
On 7 Aug 2022, at 17:28, Jay Sulzberger via Gnupg-users
wrote:
Andrew, do the sks keyservers work today?
I was a
> On 7 Aug 2022, at 17:28, Jay Sulzberger via Gnupg-users
> wrote:
>
> Andrew, do the sks keyservers work today?
>
> I was able to find the key by going to
>
> https://keyserver.ubuntu.com/
>
> and putting
>
> EC6C2905F0F93C0373946CA10642427A5FF780BE
>
> into the search box.
Do you mean S
On Sat, 6 Aug 2022, Andrew Gallagher via Gnupg-users, Andrew Gallagher
, wrote:
On 06/08/2022 13:49, Jay Sulzberger via Gnupg-users wrote:
I think the Washington Post has not placed their recent key on the PGP
public keyservers.?? Below is quoted from a different machine:
?? Welcome to the
Michael Richardson wrote:
> Yeah, the marketing department screwed it up, and should have put
> on it. It suggests that it has never really been used.
I sent an encrypted email to the newspaper, pointing them at this thread, and
the problems they have.
signature.asc
Description: PGP
On Sat, 6 Aug 2022, Andrew Gallagher via Gnupg-users
wrote:
On 06/08/2022 13:49, Jay Sulzberger via Gnupg-users wrote:
I think the Washington Post has not placed their recent key on the PGP
public keyservers.?? Below is quoted from a different machine:
?? Welcome to the Emacs shell
?? ~
27;
gpg: keyserver receive failed: No data
~ $
As this key's availability is in the public interest, and does not
contain any personal information, I have taken the liberty of submitting
it to the SKS network.
A
OpenPGP_0xFB73E21AF1163937_and_old_rev.asc
Description: Ope
On 06/08/2022 13:49, Jay Sulzberger via Gnupg-users wrote:
I think the Washington Post has not placed their recent key on the PGP
public keyservers. Below is quoted from a different machine:
Welcome to the Emacs shell
~ $ gpg --recv-keys 'EC6C2905F0F93C0373946CA10642427A5FF780BE'
gpg:
On Fri, 5 Aug 2022, Francesco Ariis wrote:
Hello Jay,
Hi, Francesco!
Il 05 agosto 2022 alle 17:28 Jay Sulzberger via Gnupg-users ha scritto:
> Does the PGP public key at https://www.washingtonpost.com/anonymous-news-tips/
> work?
It gets copied in a weird way (i.e. some character
v-keys 'EC6C2905F0F93C0373946CA10642427A5FF780BE'
gpg: keyserver receive failed: No data
~ $
oo--JS.
- below from Michael Richardson's response --
-----Begin PGP PUBLIC KEY BLOCK-
Version: Mailvelope v4.6.0
Comment: https://www.mailvelope.com
xsDNBGLr60kBDAC7/dyy27fxfbaE1Ss13QI9li
2022 alle 17:28 Jay Sulzberger via Gnupg-users ha scritto:
> >> Does the PGP public key at
> >> https://www.washingtonpost.com/anonymous-news-tips/ work?
>
> > It gets copied in a weird way (i.e. some characters that should be
> > newlines are instead
Il 05 agosto 2022 alle 18:13 Michael Richardson ha scritto:
> Francesco Ariis wrote:
> > Il 05 agosto 2022 alle 17:28 Jay Sulzberger via Gnupg-users ha scritto:
> >> Does the PGP public key at
> >> https://www.washingtonpost.com/anonymous-news-tips/ work?
&
Francesco Ariis wrote:
> Hello Jay,
> Il 05 agosto 2022 alle 17:28 Jay Sulzberger via Gnupg-users ha scritto:
>> Does the PGP public key at
>> https://www.washingtonpost.com/anonymous-news-tips/ work?
> It gets copied in a weird way (i.e. some char
The key on that page is line wrapped.
If I replace the right spaces with newlines, then it seems to work import okay.
-BEGIN PGP PUBLIC KEY BLOCK-
Version: Mailvelope v4.6.0
Comment: https://www.mailvelope.com
xsDNBGLr60kBDAC7/dyy27fxfbaE1Ss13QI9li93YePYFNjLW1JonvNcsmN
Hello Jay,
Il 05 agosto 2022 alle 17:28 Jay Sulzberger via Gnupg-users ha scritto:
> Does the PGP public key at https://www.washingtonpost.com/anonymous-news-tips/
> work?
It gets copied in a weird way (i.e. some characters that should be
newlines are instead spaces); I am not able to imp
work?
Thank you for reading this!
I remain, as ever, your fellow student of history and probability,
Jay Sulzberger
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
Am Mo den 31. Jan 2022 um 22:39 schrieb jonkomer via Gnupg-users:
> But the reason for my original post was not to find
> better ways of communication mechanics while the
> relationship exists, it was specific and quite narrow:
> how can both sides do all they reasonably can in order
> to avoid mak
On 31-01-2022 18:11, Andrew Gallagher via Gnupg-users wrote:
> This is incorrect. All three of the commonly-used HKP servers can remove
> keys; this has been done for years to remove poison (i.e. oversized)
> keys that cause DoS. However doing so comes with costs.
Yes, that was the issue that I k
This sounds like a perfect use case for WKD
You are correct.
But the reason for my original post was not to find
better ways of communication mechanics while the
relationship exists, it was specific and quite narrow:
how can both sides do all they reasonably can in order
to avoid making it p
> On 31 Jan 2022, at 21:39, jonkomer wrote:
>
> There is significant difference between a one-time
> "third-party" correspondent misusing his knowledge of
> the relationship after it has been dissolved, from
> that same knowledge being published in perpetuity via
> a simple, automated Internet
the one
> that needs this level of control: he insists on the ability
> to positively respond to individual e-mail users' GDPR
> "forget me" requests.
...
> Domain owner intends to operate a "members only" public key
> dissemination and fingerprint verification mec
On 29/01/2022 01:55, Johan Wevers via Gnupg-users wrote:
> There are known technical issues: the HKP keyserver does not allow keys
> to be removed, GDPR or not. When the keyserer operator operates outside
> of the EU I don't think that is a legal problem.
This is incorrect. All three of the common
On 29/01/2022 03:51, Shawn K. Quinn via Gnupg-users wrote:
> If the server is physically in the US, administered by someone residing
> in the US, is the EU really expecting US courts to enforce EU
> laws/directives like the GDPR on a US citizen?
The short answer is no, of course not.
The practica
Unrelated note: I find the rhetoric of a few posts in this thread
absolutely astounding. From a crypto question to red scare and "my army
is going to kick your country's ass if it dares talk to me" in two easy
steps ? This is vile.
"Tell it to the Marines" is a standard American and British prov
On Fri, 28 Jan 2022 13:02:03 -0700, jonkomer via Gnupg-users
wrote:
> After the user removal the domain owner is ipso facto
> GDPR compliant. However, he would prefer that a naive user
> (rightly or not) does not consider him unresponsive, and both
> sides have some interest in preventing any Int
PS: I guess by the "emotional reactions" you mean Robert J. Hansen
mails, since replies by other people seem much more technical in
nature.
If by 'emotional' people mean 'amused', then yes. I thought it was
cuter than a pailful of kittens. :)
If by 'emotional' people mean angry, annoyed, or
(changing back the thread subject)
On 2022-01-29 at 09:38 -0700, jonkomer wrote:
> I was the one to suggest to them to use e-mail and OpenPG
> encryption. The reasons were two-fold: first to avoid one of
> those centralized, web-browser based, single-point-of-failure,
> essentially insecure commun
On 2022-01-28 at 20:43 -0700, jonkomer wrote:
> > When the keyserer operator operates outside
> > of the EU I don't think that is a legal problem.
>
> If an individual that requests his personal information is
> removed (i.e., the "right to be forgotten") is EU resident,
> GDPR applies regardless
On 29-01-2022 4:43, jonkomer via Gnupg-users wrote:
>> When the keyserer operator operates outside
>> of the EU I don't think that is a legal problem.
> If an individual that requests his personal information is
> removed (i.e., the "right to be forgotten") is EU resident,
> GDPR applies regardle
If an individual that requests his personal information is
removed (i.e., the "right to be forgotten") is EU resident,
GDPR applies regardless of the jurisdiction in which the
information server is located.
"Right to be forgotten" doesn't exist in the United States. It's a
violation of our Fir
On 1/28/22 21:43, jonkomer via Gnupg-users wrote:
> If an individual that requests his personal information is
> removed (i.e., the "right to be forgotten") is EU resident,
> GDPR applies regardless of the jurisdiction in which the
> information server is located.
>
> Jon K.
If the server is phys
jonkomer via Gnupg-users wrote:
When the keyserer operator operates outside
of the EU I don't think that is a legal problem.
If an individual that requests his personal information is
removed (i.e., the "right to be forgotten") is EU resident,
GDPR applies regardless of the jurisdiction in whic
When the keyserer operator operates outside
of the EU I don't think that is a legal problem.
If an individual that requests his personal information is
removed (i.e., the "right to be forgotten") is EU resident,
GDPR applies regardless of the jurisdiction in which the
information server is locat
On 28-01-2022 21:02, jonkomer via Gnupg-users wrote:
> How do individual key-server owner/operators react to
> formal GDPR "forget me" requests; either by e-mail users, or
> by mail domain owners? Any known legal precedents?
There are known technical issues: the HKP keyserver does not allow keys
To this
end it is desirable to give the users the option to
create "personalized" mail account addresses (i.e.,
) and include their first/last
name in the public key.
Domain owner intends to operate a "members only" public key
dissemination and fingerprint verification mechan
On 26/01/2022 22:03, jonkomer via Gnupg-users wrote:
> Is there anything that a public key owner can do, to actually
> *ensure* that, if some careless or malicious correspondent
> ignores the comment ("Please do not upload...") and attempts
> to upload his or her (othe
Is there anything that a public key owner can do, to actually
*ensure* that, if some careless or malicious correspondent
ignores the comment ("Please do not upload...") and attempts
to upload his or her (otherwise fully functional) public key
to the key-server(s), the key upload is rej
I received a smime message from a colleague (with his public key
> embedded of course).
> When I tried to send him a smime encrypted and signed message I obtained
> the lisp error:
> Debugger entered--Lisp error: (epg-error "Encrypt failed" "Unusable public
> key:
On Sun, 26 Dec 2021 09:20, Uwe Brauer said:
> gpgsm (GnuPG) 2.1.11
Please get a decent version. The LTS branch is currently at 2.2.33.
Your version is 5 years old!
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
signature.asc
Description: PGP signatu
Hi
I am on Ubuntu 16.04 running
gpgsm (GnuPG) 2.1.11
libgcrypt 1.6.5
libksba 1.3.3-unknown
I am also a die hard user of emacs and use it for encrypting and
decrypting my mails.
I received a smime message from a colleague (with his public key
embedded of course).
When I tried to send him a
> Don't do that. Seriously. This is like saying "I want to learn how to
> farm like my grandparents did!" Farming is hard enough: voluntarily
> doing without, you know, *electricity* is just crazy. (In the United
> States, many farms were without electricity until the 1940s!)
> These easy-to-u
Am 18.12.21 um 19:07 schrieb Ingo Klöcker:
> On Freitag, 17. Dezember 2021 18:04:04 CET S.B. via Gnupg-users wrote:
>>> Otherwise, you can simply send your exported key to the person you want to
>>> give your public key to.
>>
>> Yeah so, I can attach the
1 - 100 of 819 matches
Mail list logo
