Re: [SOLVED] Re: thunderbird can not import gpg-key

On Sat, Mar 25, 2023 at 04:18:28PM +0100, Hans wrote: > I am answering myself. >... > Then I could export the keys using the correct syntax (name of the key, not > some filename). Probably like gpg --export-secret-key 8A7F208C6D9E73291657414D2135D123D8C19BEC > precious

[SOLVED] Re: thunderbird can not import gpg-key

which led to a new error. Reverting this, I tried "gpg -K" and then saw the keys with its name. Then I could export the keys using the correct syntax (name of the key, not some filename). Such I got a new file, which could be imported into thunderbird. So, one mistake led to

Re: thunderbird can not import gpg-key

* 2023-03-25 14:37:10+0100, Hans wrote: > I tried, but ran into the same issue: > > LANG=C gpg --export-secret-key > /home/ullhan63/.gnupg/private-keys-v1.d/123456789.key > testkey Wrong argument. "gpg --export-secret-key" does not want filename argument. It wants k

Re: thunderbird can not import gpg-key

Hmm, maybe it is because I changed the permissions during my testing purposes. I reset them to original and tried again. The error is gone, but nothing is exported. Ok, thanks guys, I will try some more. Maybe kleopatra is interfeering with my keys. If I know more, I will let you know. Best

Re: thunderbird can not import gpg-key

On Sat, Mar 25, 2023 at 02:37:10PM +0100, Hans wrote: > LANG=C gpg --export-secret-key > /home/ullhan63/.gnupg/private-keys-v1.d/123456789.key > > testkey > gpg: WARNING: unsafe permissions on homedir '/home/myusername/.gnupg' > gpg: WARNING: nothing exported >

Re: thunderbird can not import gpg-key

Hi Geert, I tried, but ran into the same issue: LANG=C gpg --export-secret-key /home/ullhan63/.gnupg/private-keys-v1.d/123456789.key > testkey gpg: WARNING: unsafe permissions on homedir '/home/myusername/.gnupg' gpg: WARNING: nothing exported Strange. Best regards Ha

Re: thunderbird can not import gpg-key

yusername". > > However, even if I set the rights to "everybody can read it" (what is > of course only set for testing purposes!) it does not work. > > Anything else, where I should take a look? If I recall correct, I did something like gpg --export-secret-ke

thunderbird can not import gpg-key

Hi folks, I wanted to import my secret key into thunderbird, but thunderbird can not read the directory. What an I doing wrong? I do (my thunderbird is in German, so my English translation might not be quite accurate): - starting thunderbird - chose in "Open PGP" the option "add key" - cl

Re: Cannot open *.asc files with gpg -- because no pinentry

On 2023-01-06 22:48, Jerome BENOIT wrote: Hi, I had some similar issue a long time ego. So far I can remember the following page was very useful, in particular section 9.2: https://wiki.archlinux.org/title/GnuPG best, Jerome Thanks for the tip, it looks good. When I have a chance to test

Re: Cannot open *.asc files with gpg -- because no pinentry

On 06/01/2023 11:38, Ken Heard wrote: When I try to do so I receive the following message: [GNUPG:] ENC_TO 091EE1D5633F19F2 16 0 [GNUPG:] KEY_CONSIDERED 7D605C8CDA5240843A6B9A8394D949CCE9099937 0 [GNUPG:] KEY_CONSIDERED 7D605C8CDA5240843A6B9A8394D949CCE9099937 0 gpg: encrypted with 4096-bit

Cannot open *.asc files with gpg -- because no pinentry

When I try to do so I receive the following message: [GNUPG:] ENC_TO 091EE1D5633F19F2 16 0 [GNUPG:] KEY_CONSIDERED 7D605C8CDA5240843A6B9A8394D949CCE9099937 0 [GNUPG:] KEY_CONSIDERED 7D605C8CDA5240843A6B9A8394D949CCE9099937 0 gpg: encrypted with 4096-bit ELG key, ID 091EE1D5633F19F2, created

Re: GPG problems

On Sun, Dec 04, 2022 at 04:28:00PM +0200, Teemu Likonen wrote: > * 2022-12-04 12:05:56+, Alain D. D. Williams wrote: > > > Part of the problem is the hopeless message "Server indicated a > > failure" which says little. Any idea how I could get something more > > informative ? > > You can chan

Re: GPG problems

* 2022-12-04 12:05:56+, Alain D. D. Williams wrote: > Part of the problem is the hopeless message "Server indicated a > failure" which says little. Any idea how I could get something more > informative ? You can change debug logging level. Edit ~/.gnupg/dirmngr.conf file and write something l

Re: GPG problems

ian 10, both attempts within a few minutes of each other, both connect to hkps://keys.openpgp.org Both run the same version of gpg (GnuPG) 2.2.27 (I installed from backports on Debian 10) gpg reports the version of libgcrypt On Debian 10 it is 1.8.4 on Debian 11 it is 1.8.8 Could that be an

Re: GPG problems

On Sat, Dec 3, 2022 at 12:42 PM Alain D D Williams wrote: > > I am running Debian 10 (buster). I generated a new key that I wanted to > upload, > but it fails: > > $ gpg --send-keys 0xBA366B977C06BAF7 > gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org > gp

GPG problems

I am running Debian 10 (buster). I generated a new key that I wanted to upload, but it fails: $ gpg --send-keys 0xBA366B977C06BAF7 gpg: sending key 0xBA366B977C06BAF7 to hkps://keys.openpgp.org gpg: keyserver send failed: Server indicated a failure gpg: keyserver send failed: Server indicated a

Re: gpg says no user ID

Dragonette:/home/tom/Downloads/debian# gpg2 --verify SHA512SUMS.sign.txt debian-11.5.0-amd64-netinst.iso gpg: Signature made Sat 10 Sep 2022 07:00:08 PM EDT gpg:    using RSA key DF9B9C49EAA9298432589D76DA87E80D6294BE9B gpg: BAD signature from "Debian CD signing key " [unknown]

Re: gpg says no user ID

Good to let users of gpg know credentials have no web of trust so verification of credentials will remain limited until further public and official notice. Public and official notice ought to include an announcement email to all debian email lists in the event these credentials are ever added to

Re: gpg says no user ID

--verify SHA512SUMS.sign.txt debian-11.5.0-amd64-netinst.iso gpg: Signature made Sat 10 Sep 2022 07:00:08 PM EDT gpg:    using RSA key DF9B9C49EAA9298432589D76DA87E80D6294BE9B gpg: BAD signature from "Debian CD signing key " [unknown] Note: I used SHA512SUMS.sign.txt and SHA5

Re: gpg says no user ID

Hi, i managed to produce a rare self-misattribution by copy+paste: - the program gpg writes about the Debian CD signing key DA87E80D6294BE9B : > > > WARNING: This key is not certified with a trusted signature! >

Re: gpg says no user ID

Hi, the program gpg writes about the Debian CD signing key DA87E80D6294BE9B : > > > WARNING: This key is not certified with a trusted signature! > > > There is no indication that the signature belongs to the owner I wrote: > > This is a security usability problem. How

Re: gpg says no user ID

r. > > There's no need for starting over. The SHA512SUM file is meanwhile > authenticated by your run of: > > > > gpg2 --verify SHA512SUMS.sign SHA512SUMS > > > [...] > > > gpg: Good signature from "Debian CD signing key > > > " [unkn

Re: gpg says no user ID

On 11/16/22 09:13, Thomas Schmitt wrote: Hi, Thomas George wrote: I am going to erase every thing I have done and start over. There's no need for starting over. The SHA512SUM file is meanwhile authenticated by your run of: gpg2 --verify SHA512SUMS.sign SHA512SUMS [...]    gpg:

Re: gpg says no user ID

Hi, Thomas George wrote: > I am going to erase every thing I have done and start over. There's no need for starting over. The SHA512SUM file is meanwhile authenticated by your run of: > > gpg2 --verify SHA512SUMS.sign SHA512SUMS > > [...] > >   gpg: Good signature f

Re: gpg says no user ID

Am 15.11.2022 um 19:20 schrieb Jeffrey Walton: > It's not you. The whole key server architecture is a mess nowadays. > > Jeff Thank you, Jeff, for your explanation and hints. Just one additional viewpoint from me (an afficionado for data protection) ;-) As i see it, the european law suffers fro

Re: gpg says no user ID

emands of the current landscape. I just shake my head in disbelief at what things have come to. It makes me want to unsubscribe from the GnuPG mailing lists... For example, from "keyserver receive failed: No name - for gpg --keyserver hkp://pool.sks-keyservers.net," https://lists.gnupg.org/

Re: gpg says no user ID

Am 14.11.2022 um 23:17 schrieb Thomas George: > I am still trying to do a fully verified installation of debian-11.5.0. > > gpg --verify SHA512SUMS.sign SHA512SUMS responded with DF98...BE9B > > gpg --recv-keys DF98...BE9B responded key DF98...BE9B: new key but > contains no

Re: gpg says no user ID

Hi, Thomas George wrote: > gpg2 --verify SHA512SUMS.sign debian-11.5.0-amd64-netinst.iso > ...gpg: BAD signature from "Debian CD signing key Consider to re-read my mail of yesterday: Date: Mon, 14 Nov 2022 09:19:29 +0100 Subject: Re: No Public Key https://lists.debian.org/debia

Re: gpg says no user ID

On Tue, Nov 15, 2022 at 12:22 PM Thomas George wrote: > > Close, almost there. At the end something goes wrong. Here is the output: > > gpg2 keyserver keyring.debian.org --recv DF98...BE9B > > gpg: /root/.gnupg/trustdb.gpg: trust.db created > > gpg: key DA87

Re: gpg says no user ID

Close, almost there.  At the end something goes wrong. Here is the output: gpg2 keyserver keyring.debian.org --recv DF98...BE9B    gpg: /root/.gnupg/trustdb.gpg: trust.db created    gpg: key DA87E80D6294BE9B: public key "Debian CD signing  key " imported    gpg: Total number pr

Re: gpg says no user ID

On Mon, Nov 14, 2022 at 05:17:25PM -0500, Thomas George wrote: > I am still trying to do a fully verified installation of debian-11.5.0. > > gpg --verify SHA512SUMS.sign SHA512SUMS responded with DF98...BE9B > > gpg --recv-keys DF98...BE9B responded key DF98...BE9B: new key bu

Re: gpg says no user ID

4 Nov 2022, Thomas George wrote: > I am still trying to do a fully verified installation of debian-11.5.0. > > gpg --verify SHA512SUMS.sign SHA512SUMS responded with DF98...BE9B > > gpg --recv-keys DF98...BE9B responded key DF98...BE9B: new key but contains no > user ID - skipped.

gpg says no user ID

I am still trying to do a fully verified installation of debian-11.5.0. gpg --verify SHA512SUMS.sign SHA512SUMS responded with DF98...BE9B gpg --recv-keys DF98...BE9B responded key DF98...BE9B: new key but contains no user ID - skipped. Another source suggested gpg --key-server

Re: gpg-agent, smartcard remembers PIN forever

* 2022-02-15 07:24:51-0500, Henning Follmann wrote: > I do have my private keys on a smartcard. Everything works fine, > but I noticed that gpg-agent does not forget the PIN of the card > It just remembers it forever (as long as the card remains inserted). > I have to physicall

Re: gpg-agent, smartcard remembers PIN forever

On Tue, 15 Feb 2022 at 23:25, Henning Follmann wrote: > I do have my private keys on a smartcard. Everything works fine, > but I noticed that gpg-agent does not forget the PIN of the card > It just remembers it forever (as long as the card remains inserted). > I have to physicall

gpg-agent, smartcard remembers PIN forever

Hello, I do have my private keys on a smartcard. Everything works fine, but I noticed that gpg-agent does not forget the PIN of the card It just remembers it forever (as long as the card remains inserted). I have to physically remove the smartcard to wipe the PIN. It might be also a problem of

Re: Impossible to verify GPG signature on Debian Release file

On 11/23/2021 4:16 PM, john doe wrote: On 11/23/2021 1:49 PM, deloptes wrote: john doe wrote: What am I missing? this specific key seems not to be available on the debian keyserver try keyserver.ubuntu.com, you can find the key there Thank you. The Ubuntu keyring is: keyserver.ubuntu.c

Re: Impossible to verify GPG signature on Debian Release file

On 11/23/2021 1:49 PM, deloptes wrote: john doe wrote: What am I missing? this specific key seems not to be available on the debian keyserver try keyserver.ubuntu.com, you can find the key there Thank you. -- John Doe

Re: Impossible to verify GPG signature on Debian Release file

john doe wrote: > What am I missing? this specific key seems not to be available on the debian keyserver try keyserver.ubuntu.com, you can find the key there -- FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0

Impossible to verify GPG signature on Debian Release file

Debians, I'm trying to verify the Debian's Release file but to no avail: $gpg --keyserver keyring.debian.org --keyserve r-options auto-key-retrieve --verify Release.gpg Release gpg: Signature made 10/9/2021 11:35:49 AM Romance Daylight Time gpg:usi

Re: reprepro using a gpg certificate

Andreas Ronnquist writes: On Mon, 28 Sep 2020 15:01:25 +0200, Philipp Ewald wrote: >afaik: > >you dont need a password on a gpg-key so if its not required you can >remove the password and script That is right of course - but how is this security-wise? I guess in my case it doesn&#

Re: reprepro using a gpg certificate

On Mon, 28 Sep 2020 15:01:25 +0200, Philipp Ewald wrote: >afaik: > >you dont need a password on a gpg-key so if its not required you can >remove the password and script > That is right of course - but how is this security-wise? I guess in my case it doesn't matter much

Re: reprepro using a gpg certificate

orks just >> fine, with one small exception: >> >> After I dput a package I must login to the repository server, and run >> a shell script containing the reprepro command, which I cannot >> automate, since it requests entry of a password for a gpg key. >> >

Re: reprepro using a gpg certificate

afaik: you dont need a password on a gpg-key so if its not required you can remove the password and script Am 28.09.20 um 13:59 schrieb Andreas Rönnquist: Hi! I have managed to setup a personal repository for backports from unstable to stable only for personal usage. Everything works just

Re: reprepro using a gpg certificate

e I must login to the repository server, and run > a shell script containing the reprepro command, which I cannot > automate, since it requests entry of a password for a gpg key. > > Does anyone have some simple instructions to setup reprepro so I don't > have to enter this password b

reprepro using a gpg certificate

cannot automate, since it requests entry of a password for a gpg key. Does anyone have some simple instructions to setup reprepro so I don't have to enter this password by hand - I understand that I can use some kind of gpg certificate to get around this, but I haven't managed to set it u

Re: Error importing gpg key - Solved!

Reco wrote on 5/16/20 6:14 PM: sed -i '/^keyserver-options/d' ~/.gnupg/gpg.conf Thanks! Solves the problem!

Re: Error importing gpg key

Hi. On Sat, May 16, 2020 at 04:08:18PM -0500, Dennis Wicks wrote: > The tor website says to use the command > > > gpg --auto-key-locate nodefault,wkd --locate-keys torbrow...@torproject.org > > When I do that I get an error message > > > gpg: keyserver option

Error importing gpg key

The tor website says to use the command gpg --auto-key-locate nodefault,wkd --locate-keys torbrow...@torproject.org When I do that I get an error message gpg: keyserver option 'ca-cert-file' is obsolete; please use 'hkp-cacert' in dirmngr.conf I have searched the net

Re: Reply-default etiquette (was Re: KISS gpg)

On Sun, 3 Nov 2019 22:00:39 +0200 Andrei POPESCU wrote: > On Jo, 31 oct 19, 11:55:01, The Wanderer wrote: > > > > (IMO the correct behavior should be chosen automatically by > > "reply", and there should be separate "reply to sender", "reply to > > all", and "reply to list" options in the client

Re: Reply-default etiquette (was Re: KISS gpg)

On Jo, 31 oct 19, 11:55:01, The Wanderer wrote: > > (IMO the correct behavior should be chosen automatically by "reply", and > there should be separate "reply to sender", "reply to all", and "reply > to list" options in the client. I don't know of anything which > implements that, however.) I see

Re: KISS gpg

>> AFAICT the sockets are not created in GNUPGHOME, so your "gpg with other >> GNUPGHOME" will still talk to the same agent and confusion will ensue. > yes seems the only way is true a different user, as it seems to be per > design one user - one agent, which also mak

Re: KISS gpg

On 2019-10-30 18:58, Nicolas George wrote: Hi. Is there somewhere in Debian a KISS version of GnuPG or something compatible? The current default version of GnuPG, since 2015, necessarily uses a client-server agent to access the private keys. While it is convenient and secure for everyday use, b

Re: KISS gpg

Stefan Monnier wrote: > AFAICT the sockets are not created in GNUPGHOME, so your "gpg with other > GNUPGHOME" will still talk to the same agent and confusion will ensue. yes seems the only way is true a different user, as it seems to be per design one user - one agent, which als

Re: KISS gpg

>> so even changing $HOME won't help and I don't see any envvar which >> influences it.  I suggest you contact the GPG development folks (maybe >> open an issue for it). > > Not sure - cause if you close gpg and agent etc. and set the GNUPGHOME and > start a

Re: KISS gpg

Nicolas George wrote: > The problem is to run instances of gpg simultaneously: one to access the > key without any risk of modifying it, one to do the work. > Looks like the only risk is you :) How would you modify a key without wanting it?! As I mentioned before - to me it looks like

Re: [OT] Email signature double dash delimiters (Was: KISS gpg)

Cindy Sue Causey (12019-10-31): > Maybe it's only certain ones? Or maybe the correct answer has already been given twice in this very discussion: https://lists.debian.org/debian-user/2019/10/msg01140.html https://lists.debian.org/debian-user/2019/10/msg01152.html Regards, -- Nicolas George

[OT] Email signature double dash delimiters (Was: KISS gpg)

On 10/31/19, Greg Wooledge wrote: > On Fri, Nov 01, 2019 at 02:12:54AM +1100, Andrew McGlashan wrote: >> If you kill all agents to stop them interfering, then use the >> - --homedir option of gpg with a copy of your files, I think you will >> have what you need. > > Huh

Re: KISS gpg

deloptes (12019-10-31): > Not sure - cause if you close gpg and agent etc. and set the GNUPGHOME and > start again all the work will be done in the new GNUPGHOME. The sockets > will be created when you start gpg. > > What is the problem with it? How do you expect the progr

Re: KISS gpg

Stefan Monnier wrote: > so even changing $HOME won't help and I don't see any envvar which > influences it.  I suggest you contact the GPG development folks (maybe > open an issue for it). Not sure - cause if you close gpg and agent etc. and set the GNUPGHOME and start again a

Re: KISS gpg

>> So I think you're stuck with copying by hand the actual file that >> holds the private key (somewhere in ~/.gnupg) if you want to "export" >> it. Once you've done that, you can put it in "another-dir" with >> a similar structure and the

Re: KISS gpg

On 2019-10-31, The Wanderer wrote: > > (I do understand what you probably mean by the overall statement, of > course, but linguistics is one of my interests and this has caught my > attention.) > I believe the OP is French and means 'exigent' is the usual French sense of the word---demanding, exa

Re: KISS gpg

Nicolas George wrote: > deloptes (12019-10-31): >> again the homedir option is for the agent and not for gpg - and you >> should setup your environment properly > > Again, without perfect control and feedback, this is not acceptable. > What do you mean by control and feed

Re: Reply-default etiquette (was Re: KISS gpg)

Gene Heskett (12019-10-31): > And this is something that the kmail of yore, now forked to TDE, makes > simple. If you sort incoming mail to list yy in its own folder, then it > is sufficient to name that list in the folder definitions. I've been > doing that for so long I'd consider any email a

Re: Reply-default etiquette (was Re: KISS gpg)

On Thursday 31 October 2019 12:10:01 Nicolas George wrote: > The Wanderer (12019-10-31): > > IMO, the correct behavior should indeed be the same for lists as for > > private mail: reply to the source from which you received the > > message. > > ... and everybody who got it too. > > For example, if

Re: Reply-default etiquette (was Re: KISS gpg)

Andrew McGlashan (12019-11-01): > Do you also have "ignore list-post:" in your muttrc ? Of course not. What a strange question: the ignore directive is for display, not for controlling the recipients. In case you confused it with ignore_list_reply_to, look at the comment on its side: "Press L for

Re: Reply-default etiquette (was Re: KISS gpg)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/11/19 3:10 am, Nicolas George wrote: > Possible with Mutt: > > send-hook . "unmy_hdr Reply-To:" send-hook > ~cdebian-u...@lists.debian.org my_hdr "Reply-To: > debian-user@lists.debian.org" Do you also have "ignore list-post:" in your muttrc

Re: KISS gpg

The Wanderer (12019-10-31): > ...can you clarify what you mean by this term? The definition of > "exigent" which I know of ("in need of immediate, urgent response, such > that there is not time to delay", roughly speaking), and the one I find > in gcide, doesn't seem to fit this context at all; "ex

Re: KISS gpg

deloptes (12019-10-31): > again the homedir option is for the agent and not for gpg - and you should > setup your environment properly Again, without perfect control and feedback, this is not acceptable. Regards, -- Nicolas George signature.asc Description: PGP signature

Re: Reply-default etiquette (was Re: KISS gpg)

The Wanderer (12019-10-31): > IMO, the correct behavior should indeed be the same for lists as for > private mail: reply to the source from which you received the message. ... and everybody who got it too. For example, if I reply to: # From: Colleague # To: Me # Cc: Boss it should be: # From:

Re: KISS gpg

On 2019-10-31 at 12:01, Nicolas George wrote: > Andrew McGlashan (12019-11-01): >> I'm not manually adding any reply-to header, no-one else has a >> problem with "List-Post:" header > > I will not discuss this further if your solution requires a > different command for lists and individual

Re: KISS gpg

Nicolas George wrote: > That would have worked with gpg < 2.1. With >= 2.1, it will ignore the > homedir option and connect to an agent. Or re-start an agent, with or > without the homedir option. I do not know what gpg does exactly, it does > not tell me. For handling somethin

Re: KISS gpg

Andrew McGlashan (12019-11-01): > No, if you have the file S.gpg-agent in the alternate --homedir with the > right settings that point somewhere else for the socket, you can check > it's existence before and after invoking with --homedir Maybe. This is too uncertain and hackish, I do not want to t

Re: KISS gpg

Greg Wooledge wrote: > Huh.  There's that "dash space dash dash" pattern again, from a completely > different person this time. > > Is the mailing list software mangling people's posts (lines that begin > with dash dash get an extra dash space prepended), or is there some > common mail user agent

Re: KISS gpg

Erwan David wrote: > The question was *which* product can be used. I am not aware of such that runs under linux and I do not remember the time I used pgp - but it was on company windows pc between 2002 - 2007. So this topic is pointless - IMO there is no such tool for linux. I also do not under

Re: KISS gpg

ot require that extra attention, an inferior solution should > not be chosen. > >> https://askubuntu.com/questions/777900/how-to-configure-gnupgs-s-gpg-agent-socket-location#860346 > > Requires changing files in the home directory, which makes it complex to > have several inst

Reply-default etiquette (was Re: KISS gpg)

On 2019-10-31 at 11:36, Nicolas George wrote: > Andrew McGlashan (12019-11-01): > >> btw doesn't "reply list" work for you? I get all list messages >> okay. > > If you do not want to be on copy, use the standard reply-to header > to specify it, just like me. Senders should not be expected to do

Re: KISS gpg

Andrew McGlashan (12019-11-01): > Emails of the list have a header > > List-Post: > > There should be no need for an extra reply-to header. Already replied to this: a solution whose UI treats lists and individual mails differently is optimal. Regards, --

Re: KISS gpg

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/11/19 2:36 am, Nicolas George wrote: > Andrew McGlashan (12019-11-01): >> btw doesn't "reply list" work for you? I get all list messages >> okay. > > If you do not want to be on copy, use the standard reply-to header > to specify it, just li

Re: KISS gpg

sen. > https://askubuntu.com/questions/777900/how-to-configure-gnupgs-s-gpg-agent-socket-location#860346 Requires changing files in the home directory, which makes it complex to have several instances simultaneously, and will not confirm what socket is used. Too fragile and uncertain. R

Re: KISS gpg

On 1/11/19 2:34 am, Nicolas George wrote: > At the very least, to trust gpg with its agent, I would require options > to explicitly set the path of the agent's socket and to print the path > of the socket that was used. reply-list works perfectly this end, forget what's in th

Re: KISS gpg

On qui, 31 out 2019, Greg Wooledge wrote: On Fri, Nov 01, 2019 at 02:12:54AM +1100, Andrew McGlashan wrote: If you kill all agents to stop them interfering, then use the - --homedir option of gpg with a copy of your files, I think you will have what you need. Huh. There's that "

Re: KISS gpg

Andrew McGlashan (12019-11-01): > btw doesn't "reply list" work for you? I get all list messages okay. If you do not want to be on copy, use the standard reply-to header to specify it, just like me. Senders should not be expected to do something special for normal answers, correct behaviour shoul

Re: KISS gpg

Andrew McGlashan (12019-11-01): > Okay, well if something is constantly using gpg, then it will restart > as you use it by gpg. I would stop it and see that it is stopped, > then try with --homedir it may restart the agent, but it /might/ > be for the new --homedir area. I k

Re: KISS gpg

nt might be better in /your/ control? > > No, the agent is not restarted by systemd, it is restarted by gpg > itself. btw doesn't "reply list" work for you? I get all list messages okay. A. -BEGIN PGP SIGNATURE- iHUEAREIAB0WIQTJAoM

Re: KISS gpg

nt might be better in /your/ control? > > No, the agent is not restarted by systemd, it is restarted by gpg > itself. Okay, well if something is constantly using gpg, then it will restart as you use it by gpg. I would stop it and see that it is stopped, then try with --homedir it

Re: KISS gpg

On 31/10/2019 15:22, The Wanderer wrote: On 2019-10-31 at 11:18, Greg Wooledge wrote: On Fri, Nov 01, 2019 at 02:12:54AM +1100, Andrew McGlashan wrote: If you kill all agents to stop them interfering, then use the - --homedir option of gpg with a copy of your files, I think you will have

Re: KISS gpg

Andrew McGlashan (12019-11-01): > So, perhaps the agent is restarted by systemd -- perhaps you can > disable it using systemctl commands to stop it restarting ... then > the agent might be better in /your/ control? No, the agent is not restarted by systemd, it is restarted by g

Re: KISS gpg

ing, then use the - >>> --homedir option of gpg with a copy of your files, I think you >>> will have what you need. >> >> Huh. There's that "dash space dash dash" pattern again, from a >> completely different person this time. >> >>

Re: KISS gpg

The Wanderer (12019-10-31): > FWIW, I don't see that pattern in my local copy of the message you're > replying to; on my end, the line begins with '--homedir', sans quotes. Yet, is it there: https://lists.debian.org/debian-user/2019/10/msg01136.html Regards, -- Nicolas George signature.asc

Re: KISS gpg

On 2019-10-31 at 11:22, The Wanderer wrote: > On 2019-10-31 at 11:18, Greg Wooledge wrote: > >> On Fri, Nov 01, 2019 at 02:12:54AM +1100, Andrew McGlashan wrote: >> >>> If you kill all agents to stop them interfering, then use the >>> - --homedir option of gp

Re: KISS gpg

> > On Fri, Nov 01, 2019 at 02:12:54AM +1100, Andrew McGlashan wrote: > >> If you kill all agents to stop them interfering, then use the > >> - --homedir option of gpg with a copy of your files, I think you will > >> have what you need. > FWIW, I don't

Re: KISS gpg

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, On 1/11/19 2:21 am, Nicolas George wrote: > Andrew McGlashan (12019-11-01): >> If I understand correctly, the agent is getting in your way. >> >> Killing the agent /might/ be your answer: > > Unfortunately no: using the agent is mandatory sinc

Re: KISS gpg

On 2019-10-31 at 11:18, Greg Wooledge wrote: > On Fri, Nov 01, 2019 at 02:12:54AM +1100, Andrew McGlashan wrote: > >> If you kill all agents to stop them interfering, then use the >> - --homedir option of gpg with a copy of your files, I think you will >> have what you

Re: KISS gpg

ed), or is there some > common mail user agent in the wild that's doing this? # ~ $ echo 'Hello\n-- dash dash --\nworld' | gpg --clearsign # gpg: using "CA4DC60C" as default secret key for signing # -BEGIN PGP SIGNED MESSAGE----- # Hash: SHA512 # # Hello # - --

Re: KISS gpg

it isn't gpg's agent that is getting in your way, it might be the > gnome keyring daemon instead. dpkg-query: no path found matching pattern /usr/bin/gnome-keyring-daemon > If you kill all agents to stop them interfering, then use the > - --homedir option of gpg with a copy of

Re: KISS gpg

On Fri, Nov 01, 2019 at 02:12:54AM +1100, Andrew McGlashan wrote: > If you kill all agents to stop them interfering, then use the > - --homedir option of gpg with a copy of your files, I think you will > have what you need. Huh. There's that "dash space dash dash&quo

Re: KISS gpg

e key while exporting it, without changing it on the > storage? If I understand correctly, the agent is getting in your way. Killing the agent /might/ be your answer: gpgconf --kill gpg-agent I think your private key has a pass phrase, but the agent is providing the answer without you needing

Re: KISS gpg

On Thu, Oct 31, 2019 at 03:35:41PM CET, deloptes said: > Nicolas George wrote: > > > I can stop replying to you. But I can also hope that somebody will have > > a relevant answer. > > > > Sorry to not have been awed by gratefulness at your irrelevant answer. > > I already said you can use anoth

Re: KISS gpg

Nicolas George wrote: > I can stop replying to you. But I can also hope that somebody will have > a relevant answer. > > Sorry to not have been awed by gratefulness at your irrelevant answer. I already said you can use another product.

  1   2   3   4   5   6   7   8   9   10   >