On Tue, Jun 5, 2012 at 6:43 PM, Mathieu Jolicoeur wrote:
> On this topic, I have found the following thread on the GPF forums,
> which lead me back to this list.
>
> https://www.privacyfoundation.de/forum/viewtopic.php?f=13&t=1145
This could be pretty much the same issue which Edmond and Kevin ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/05/2012 05:46 PM, Richard wrote:
>
> This could be pretty much the same issue which Edmond and Kevin
> are experiencing:
>
> http://lists.gnupg.org/pipermail/gnupg-users/2012-April/044195.html
>
>
http://lists.gnupg.org/pipermail/gnupg-users
On Monday 04 June 2012, Robert J. Hansen wrote:
> Also, if there are any questions you feel are missing, throw them out
> too. Thank you!
An addition for 4.11:
Kontact [http://userbase.kde.org/Kontact]/Kontact Touch
[http://userbase.kde.org/Kontact_Touch]
Plugin? No (natively supported)
Support
On Tue, 5 Jun 2012 18:43, m...@spoked.ca said:
> Somehow, gpg2 is not able to read the key from the card. Is this a
> known bug? I have not found anyone else documenting this.
I don't have a crypto stick, thus I can't test it.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen re
On 6/5/12 8:56 AM, Werner Koch wrote:
> Some time ago I added custom ids to most questions; for example:
I can add these: it shouldn't be a problem. The reason I'm using XHTML,
incidentally, is to make it as easy as possible for you to convert it
into org-mode: an hour's work with a SAX parser sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I have recently generated subkeys to use with a GPF Cryptostick. I
decided to make full use of the ability to use 4096 bit keys with
recent versions of GnuPG ( > 2.0.18 I think). Everything is working
except when trying to decrypt a file or m
On Tue, 5 Jun 2012 15:01, klaus.la...@gmx.de said:
> I found ticket https://bugs.g10code.com/gnupg/issue1238 which describes this
> error. Are there any plans to downport the fix described in the ticket to
> 2.0.X.
The fix seems to be this:
commit 2d91febbd8d30beb7eb33f7aa80ffd5691d1d3cc
A
On Tue, 5 Jun 2012 15:24, lists.gn...@mephisto.fastmail.net said:
> I don't know if this is a coincidence or not, but I will mention that
> for the first time in a long while, Mutt segfaulted when I tried to
> open a message on the gnupg mailing list... presumably when it tried
I see two reasons
Hi,
when I remove a cryptostick and try to access it with i.e. gpg2 --card-status
I get an error
gpg: selecting openpgp failed: ec=6.32848
gpg: OpenPGP card not available: general error
In this case scdaemon log shows
scdaemon[4167]: chan_7 <- SERIALNO openpgp
2012-06-05 14:35:39 scdaemon[4167
On Mon, Jun 04, 2012 at 09:11:13PM +0200 Also sprach Werner Koch:
> On Mon, 4 Jun 2012 18:35, lists.gn...@mephisto.fastmail.net said:
>
> > require extensive manual configuration for it to work properly (but if
> > you're using Mutt, you already know that). See
> > http://wiki.mutt.org/?MuttGuide
On Tue, 5 Jun 2012 13:24, r...@sixdemonbag.org said:
> text and layout. If anyone has recommendations about this, please speak
> up now. With luck, we can have this thing to Werner by the end of the
Some time ago I added custom ids to most questions; for example:
** What is the recommended
reflum,
On Tue, 2012-06-05 at 10:20 +0530, Amol Patil wrote:
> Currenlty I am having problem with the decryption of the file my code
> is like this
>
> echo shell_exec("echo $passphrase | $gpg --passphrase-fd 0 -o
> $unencrypted_file -d $encrypted_file");
If you do this the passphrase can
> The signer himself/herself should not upload the sign key block to a key
> server, or publish it in any other way, without the certificate's owner
> explicit authorization or request.
The new text reads,
"Finally, if you have elected to make a normal signature you may wish to
upload the newly-s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04.06.2012 18:57, Sam Smith wrote:
>
> No, the exported file is NOT protected by the passphrase.
>
> If I export the key. And then delete my secret key from my keyring.
> And now Import what I exported, I am not asked for a password
> before the i
Hi,
IMHO (Open)PGP's good repudiation comes to great extend from the fact,
that it does not require rigor policies to use the keys. It is an
ad-hoc scheme and that is what differences it from S/MIME and PKIX.
It was my fault that I once set the no-modify flag for all new keys. In
practice this
On 6/5/2012 5:22 AM, gn...@lists.grepular.com wrote:
> FWIW, until I read somebody complaining about people uploading key
> signatures, instead of sending them to the key owner, it never
> occurred to me that it could possibly be a problem for anyone.
I'll go one step further: my personal belief i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/06/12 02:36, Robert J. Hansen wrote:
>> I believe the etiquette is that the signed key block should be
>> returned to the certificate's owner, for her/him to do what
>> he/she deems convenient, e.g. upload it to a keyserver.
>
> I haven't found
17 matches
Mail list logo
