RE: Passphrase Pop up

ian.maclauch...@smartstream-stp.com www.smartstream-stp.com -Original Message- From: Werner Koch Sent: 27 July 2020 11:13 To: Dmitry Alexandrov Cc: Ian Maclauchlan ; gnupg-users@gnupg.org Subject: Re: Passphrase Pop up On Mon, 27 Jul 2020 02:41, Dmitry Alexandrov said: > GnuPG versio

Re: Passphrase Pop up

On Mon, 27 Jul 2020 02:41, Dmitry Alexandrov said: > GnuPG version 3 does not exist yet. The stable release is 2.2.21. The OP probably meant Gpg4win 3.1.12 which is our Windows installer featuring GnuPG 2.2.21, Kleoptra, and our Outlook plugin. Shalom-Salam, Werner -- Die Gedanken sind f

Re: Passphrase Pop up

Ian Maclauchlan wrote: > Hi there we recently upgrade our Windows server from 2008 to 2019 and Gnu to > 3.1.12 ?? GNU is a vague operating system (just like, e. g., ‘UNIX’) and it has no versions per se. GnuPG version 3 does not exist yet. The stable release is 2.2.21. I guess, you mean Gnu

Re: Passphrase Pop up

If this is run as a scheduled task and with the passphrase kept in a text file, perhaps just remove the passphrase? On 2020-07-25T07:30:50+ Ian Maclauchlan wrote 8.1K bytes: > Hi there we recently upgrade our Windows server from 2008 to 2019 and Gnu to > 3.1.12 > > Since then the command

Re: Passphrase window freezes my DE's panel - is this a bug?

First of all, you have created three threads about it. When you reply to an email, you need to actually reply that mail. Just using the same subject does not make the email get into the thread (could you imagine the threads for emails title "Bug"?). I am replying to the original thread, and glossi

Re: Passphrase window freezes my DE's panel - is this a bug?

> On 27 Apr 2020, at 01:15, Scott C Jacobs via Gnupg-users > wrote: > > the passphrase window allows > nothing to happen until I enter the passphrase and click OK or click on > cancel. This is definitely not pinentry then. It’s most likely a unified desktop passphrase manager such as gnome-k

Re: Passphrase window freezes my DE's panel - is this a bug?

> If using the clipboard is unsafe, then GPG would disallow its use in > password managers as well, would it not? How would it do so? > If one is supposed to have long, complicated, > difficult-to-remember-and-type passwords (which one cannot even see > when they are being entered!), then one HAS

Re: Passphrase window freezes my DE's panel - is this a bug?

On 20200426, Scott C Jacobs via Gnupg-users wrote: The problem is, that even if I have a terminal window open into which I wanted to type xwininfo and xprop, once the passphrase window appears, I cannot use the terminal or anything else - the passphrase window allows nothing to happen until I e

Re: Passphrase window freezes my DE's panel - is this a bug?

On 4/26/20 1:53 PM, Scott C Jacobs via Gnupg-users wrote: The problem is, that even if I have a terminal window open into which I wanted to type xwininfo and xprop, once the passphrase window appears, I cannot use the terminal or anything else - the passphrase window allows nothing to happen unt

Re: Passphrase window freezes my DE's panel - is this a bug?

>To find out what process is controlling a window, you could use xwininfo and >xprop as described in this SO answer: >https://unix.stackexchange.com/a/84981 The problem is, that even if I have a terminal window open into which I wanted to type xwininfo and xprop, once the passphrase window appea

Re: Passphrase window freezes my DE's panel - is this a bug?

> On 26 Apr 2020, at 05:04, Scott C Jacobs via Gnupg-users > wrote: > > I don't know which of the many GPG packages throws up the passphrase window, > to know to which package a bug > report should be directed (if it is a bug). I might have thought > pinentry[*], but it is NOT one of the upg

Re: Passphrase and Key Structure

Thanks for the reply... Probably safer to back them up again just in case I forget it, especially since I have another program that uses PGP to encrypt/decrypt archives. On 1/26/2020 5:56 PM, Ángel wrote: > On 2020-01-17 at 06:47 -0700, Mark wrote: >> I was wondering what effect changing the passp

Re: Passphrase and Key Structure

On 2020-01-17 at 06:47 -0700, Mark wrote: > I was wondering what effect changing the passphrase has on the keys. Not > only the keygrip file but also on the exported copy of it that can be > used with other programs. If you change the passphrase, do you need to > re-backup those keygrip files and r

Re: Passphrase cache w/Yubikey varies: sign vs auth

On 04/09/2017 08:49 PM, NIIBE Yutaka wrote: > Steve McKown wrote: >> Can someone explain why ssh after sign asks for the passphrase again, >> and what I might be able to do to avoid this condition? It's not a big >> deal, but I do wonder if it suggests a misconfiguration on my part. > > It is no

Re: Passphrase cache w/Yubikey varies: sign vs auth

Steve McKown wrote: > Can someone explain why ssh after sign asks for the passphrase again, > and what I might be able to do to avoid this condition? It's not a big > deal, but I do wonder if it suggests a misconfiguration on my part. It is not misconfiguration. It is expected behavior. Please

Re: passphrase recovery

On 05/09/14 00:13, Parker Boxell wrote: > Hello, I am contacting you because I need help recovering my > passphrase. is there any way to accomplish this? Basically my laptop > screen broke now and I need to decrypt my word file that has my > product keys but I cannot remember for the life of me wha

Re: Passphrase

On Apr 26, 2011, at 6:38 PM, Stephen H. Dawson wrote: > Hi, > > > Dire need, hoping for help. > > I have my private and public keys, but you have neither the passphrase nor a > revocation certificate. I need to revoke my published key. Can they > recommend a bash script to discover the p

Re: Passphrase

Stephen H. Dawson wrote: > Dire need, hoping for help. > > I have my private and public keys, but you have neither the passphrase > nor a revocation certificate. I need to revoke my published key. Can > they recommend a bash script to discover the passphrase using brute > force on the private k

Re: Re: Passphrase

Hi! Am 20:59, schrieb Mark H. Wood: > someone probably could suggest a brute-force tool I tried to respond to this thread already, but somehow mixed up email settings and my relies appear to be lost, so let's try again: There's a tool called "nasty" that does 'pure' brute forcing:

Re: Passphrase

On Wed, Apr 27, 2011 at 02:29:51AM -0400, Grant Olson wrote: > Issuing a revocation would be more critical if you thought the key had > been compromised. But if the private key inaccessible to everyone, > including you, I don't think there are any exploits you need to worry about. Maybe he thinks

Re: Passphrase

On Tue, Apr 26, 2011 at 09:37:57PM -0700, Robert Holtzman wrote: > On Tue, Apr 26, 2011 at 06:38:11PM -0400, Stephen H. Dawson wrote: > > Hi, > > > > > > Dire need, hoping for help. > > > > I have my private and public keys, but you have neither the passphrase nor a > > revocation certificate

Re: Passphrase

On 04/26/2011 06:38 PM, Stephen H. Dawson wrote: > Hi, > > > Dire need, hoping for help. > > I have my private and public keys, but you have neither the passphrase > nor a revocation certificate. I need to revoke my published key. Can > they recommend a bash script to discover the passphras

Re: Passphrase

On Tue, Apr 26, 2011 at 06:38:11PM -0400, Stephen H. Dawson wrote: > Hi, > > > Dire need, hoping for help. > > I have my private and public keys, but you have neither the passphrase nor a > revocation certificate. I need to revoke my published key. Can they > recommend > a bash script to d

Re: Passphrase problem in gpgsm 2.0.14

It's fixed in gpg-agent 2.0.15 and an ubuntu bug report is filled. Please mark you are being affected by this bug so maybe the ubuntu maintainer will build a new package and include the patch. https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/567106 On Saturday, 24. April 2010 20:33:04 Alexa

Re: Passphrase problem in gpgsm 2.0.14

Hi, i am wondering if https://bugs.g10code.com/gnupg/issue1184 will get fixed any time soon? i wanted to ask this on the bugtracker's page but i think it is not possible to comment on bugs, other people reported. is this true? i really think this is a important bug, because i cannot use it as drop

Re: Passphrase problem in gpgsm 2.0.14

Am Freitag, 29. Januar 2010 17:18:33 schrieb Bernhard Reiter: > Am Dienstag, 26. Januar 2010 15:36:06 schrieb Werner Koch: > > A patch against 2.0.14 is attached. > > The signature on the email was broken for me (and for Marcus), > this is for the email received via the email list. To verify the

Re: Passphrase problem in gpgsm 2.0.14

Hi! Due to the problems with Mailman breaking the signature, I uploaded the patch from the orginal message to the ftp server and signed it: ftp://ftp.gnupg.org/gcrypt/gnupg/patches/gnupg-2.0.14-encode-s2k.patch Please apply it if you use gnupg 2.0.14 Shalom-Salam, Werner -- Die Gedank

Re: Passphrase error

Hey John, Same code that was deployed on this server has worked on 2 other servers, my dev and test servers.  The code has not been altered in anyway.  I've found that the linux admin had to tweek the new test server to get it working like the dev server.  After that tweet was made the code sta

Re: Passphrase error

Andre Lee wrote: > gpg: public key decryption failed: bad passphrase > gpg: decryption failed: secret key not available > > I've had an issue with running gpg commands via Oracle BPEL before but > the change to the new server fixed it in the TEST. Now I have this new > issues on another server i

Re: Passphrase error

Hey Guys, I'm back again with another crazy GPG issue:  I receive the following error when I run my decryption process through the Oracle BPEL process: gpg: public key is E3328CE0 gpg: using secondary key E3328CE0 instead of primary key 26C55D64 gpg: using secondary key E3328CE0 instead of pr

Re: Passphrase problem

On Tue, 20 Jan 2009 08:07:50 -0600 "Steve Brockbank" wrote: > > Can anyone tell me how to replace a passphrase in a key - when the > current passphrase is unknown ? No. Can't be done. Not possible. By design. Chris Babcock signature.asc Description: PGP signature __

Re: Passphrase problem

Steve Brockbank wrote: > > Can anyone tell me how to replace a passphrase in a key - when the current > passphrase is unknown ? If you had the forethought to generate a revocation certificate, import it and revoke the key. Generate a new key. There is absolutely no feasible way to recover a

Re: Passphrase problem

Steve Brockbank wrote: > Can anyone tell me how to replace a passphrase in a key - when the > current passphrase is unknown ? This is not possible. If it were possible, there wouldn't be much point in a passphrase in the first place. ___ Gnupg-users m

RE: Passphrase problem

Can anyone tell me how to replace a passphrase in a key - when the current passphrase is unknown ? regards steve brockbank No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.10/1903 - Release Date: 1/19/2009 8:52 PM __

Re: Passphrase storage (was Re: Protect pubring.gpg and secring.gpg)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 John W. Moore III escribió: > David Shaw wrote: > >> Out of curiousity, is anyone using one of the various passphrase >> manager sort of programs? Assuming they're implemented and used >> correctly, they're not a bad solution for passphrase overloa

Re: Passphrase storage (was Re: Protect pubring.gpg and secring.gpg)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 David Shaw wrote: > Out of curiousity, is anyone using one of the various passphrase > manager sort of programs? Assuming they're implemented and used > correctly, they're not a bad solution for passphrase overload. I use Schneier's Password Safe

Re: Passphrase caching with gpgme and gpg2

On Mon, 11 Aug 2008 18:31, [EMAIL PROTECTED] said: > Is there a timeframe when this will be fixed? And I still don't see We have no need to fix that problem. Thus it takes until all higher priority jobs are finished. > how to uses the preset-passphrase with gpgme? You can't. In most cases gpg

Re: Passphrase caching with gpgme and gpg2

On Mon, 11 Aug 2008 12:43, [EMAIL PROTECTED] said: > passphrases. What is the recommended way to handle the passphrase with > gpgme and gpg2? Since I'm building a server application I can not use You need to use gpg-preset-passphrase. I recently tested that I found that there is a buglet in gpg

Re: Passphrase caching with gpgme and gpg2

Werner Koch wrote: On Mon, 11 Aug 2008 12:43, [EMAIL PROTECTED] said: passphrases. What is the recommended way to handle the passphrase with gpgme and gpg2? Since I'm building a server application I can not use You need to use gpg-preset-passphrase. I recently tested that I found that there

Re: passphrase works ONLY with enigmail

I found the solution. I had a carefull look at Enigmail Debug Console. I found out some weird characters, that were only reproducible in a console in X mode when default locale was ISO-8859-1. In addition, the option --charset utf8 was used with gpg. I fixed to this locale, restarted X, and use

Re: --passphrase option // can two different passphrases be used in the same command?

On Wed, 28 Mar 2007 17:55, [EMAIL PROTECTED] said: > is there a way to direct gnupg to remember one passphrase for > signing, > and another one for symmetrically encrypting? Not with the --passhrase* options. You need to employ the --command-fd interface if you want better control over the pass

Re: passphrase for symmetric encryption // ?maximum length

On Wed, 24 Jan 2007 00:27, [EMAIL PROTECTED] said: > is there a maximum beyond which gnupg will just 'refuse' the > passphrase, There should be no such limit. The exception ist hat you may run out of memory. The passphrase is hold in secure memory and during computations 2 or 3 copies need to

Re: passphrase for symmetric encryption // ?maximum length

[EMAIL PROTECTED] wrote: > or is there an effective maximum, where longer passphrases make no > difference? The effective maximum is when you reach 128 bits of Shannon entropy. Using conversational English, that means about 80 characters of text. (I'm using Shannon's estimate of 1.5 bits per Engl

Re: Passphrase on the command line

Here is my idiom; checking for success is vital. See openssh documentation for details on key-based shell access. Test for transparent access, if using gpg, test for undisturbed encryption with --batch. You can pipe the dump (or tar) to gpg instead of gzip. File size will be reduced. The dd c

Re: Passphrase on the command line

Is there any documentation on how to do that? Say server A has the original data and server B has the backup. You can do from server A: backup_tool | ssh [EMAIL PROTECTED] dd of=/path/to/backup or you can do from server B: ssh [EMAIL PROTECTED] backup_tool | dd of=/path/to/backup Reg

Re: Passphrase on the command line

Stef Caunter wrote: The documentation does not recommend this. Since you appear to not want to store the ciphertext but the plaintext, an encrypted network transfer seems appropriate and less expensive. Write the backup to an ssh pipe instead of a temporary file. Is there any documentation o

Re: Passphrase on the command line

The documentation does not recommend this. Since you appear to not want to store the ciphertext but the plaintext, an encrypted network transfer seems appropriate and less expensive. Write the backup to an ssh pipe instead of a temporary file. Stef http://caunter.ca/contact.html On Wed, 22 M

Re: Passphrase problem

On Fri, 6 Jan 2006 23:41:13 +0100, Blanc Nicolas said: > And I really don't know why... Maybe a problem with KDE ? the keyboard > mapping ? Or a problem with charset ? gpg does not care about the charset for passphrases and thus if you have non-ascii in your passpharse and switch the chars

Re: Passphrase Encoding and Entropy

Hi! Please don't forget that the passphrase is only used to protect the secret key. It is a last resort protection mechanism. If someone was able to get your secret key you are better off to revoke the key and consider it compromised. The passphrase gives you some time to get the word (i.e. the

RE: Passphrase Encoding and Entropy

[Oskar L.] > Thanks for your anwser, but I'm afraid you mostly told me > what I already know. What I don't understand is how this > relates to breaking passphrases. > For example, say I use the passphrase foobar. It has 6 > characters, each represented by 8 bits, so it will be > represented by

Re: Passphrase Encoding and Entropy

On 9134 day of my life Oskar L. wrote: > Now if the attacker knows that I have only used the 23 characters > a-z in the passphrase, then she/he can represent all of them using 5 > bits. But he also knows that you use ASCII encoding for you passphrase. > But I don't understand how this helps the a

Re: Passphrase Encoding and Entropy

Bit early in the morning to try to comprehend your main question, but I can answer the question about the string to key part :). There are 3 ways to generate a key from a password outlined in the rfc: 1. Merely hashing password. 2. Salting then hashing. 3. Salting then hashing, then hashing aga

Re: Passphrase Encoding and Entropy

"Martin Geisler" <[EMAIL PROTECTED]> wrote: > When you have 64 different possibilities, all of equal likelyhood, > then you can code them using 6 bit. This is what the entropy tells > you. > > The fact that A in the 7-bit ASCII standard is 0101 is just a > coincedence --- they could just as we

Re: Passphrase Encoding and Entropy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 00:39 2005-06-06, you wrote: >Hi, > >If I'm not misinformed the passphrase can be encoded using different >character sets. Can I in gpg change witch one is used, or does it depend >on witch operating system I use? How does it affect the way you cal

Re: Passphrase Encoding and Entropy

"Oskar L." <[EMAIL PROTECTED]> writes: > Also, let's say it is known that the characters in a passphrase has > been selected from the 64 ASCII characters A-Z, a-z, 0-9, # and $. > This will give each character an entropy of 6 bits (log2(64)), witch > if I understand correctly means that 6 of the 8

Re: passphrase or random characters the safest

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 23:13 2005-05-31, Per Tunedal Casual wrote: >`- >-- >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >At 20:58 2005-05-30, you wrote: > >"Roscoe" <[EMAIL PROTECTED]> wrote: > > >

Re: passphrase or random characters the safest

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 20:58 2005-05-30, you wrote: >"Roscoe" <[EMAIL PROTECTED]> wrote: > >> Lets say there are about 10 words in your dictionary. Lets also >> say there are about 100 different characters on your keyboard. >> >> Now for password of random characters

RE: passphrase or random characters the safest

Just to inject some practicality into the discussion, a pass phrase with more than 64 bits of entropy is probably safe from all non-governmental attackers. After all, it took distributed.net five years to crack 64-bit RC5 using tens of thousands of machines. Beyond 64 bits, attacks against the end

Re: passphrase or random characters the safest

"Roscoe" <[EMAIL PROTECTED]> wrote: > Lets say there are about 10 words in your dictionary. Lets also > say there are about 100 different characters on your keyboard. > > Now for password of random characters we would need: > log(340282366920938463463374607431768211456)/log(100) 20 chars. > >

Re: passphrase or random characters the safest

Well, A 128bit key has 340282366920938463463374607431768211456 possible combinations Lets say there are about 10 words in your dictionary. Lets also say there are about 100 different characters on your keyboard. Now for password of random characters we would need: log(34028236692093846346337