-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Shaw wrote the following on 1/9/09 8:15 PM:
[...]
> It is absolutely ok and encouraged to send paperkey to whoever wants
> it. There are various ways to comply with the license (the GPL), but
> one easy way is to do what you suggest and send
On Fri, Jan 09, 2009 at 10:33:52PM -0500, Scott Lambdin wrote:
> I found a file in rejects, but it may be partial. It gives us some
> information, though.
>
> The pgp file was 406184088 bytes and unencrypted is 175246253 bytes.
>
> gpg -v -v -o a_file.out -d a_file.pgp
>
> gpg: armor: BEGIN PGP
Looks like Roscoe got it. literal data block that makes up the
difference. Thanks everyone.
Now to see if there is some reason for it.
--Scott
On Fri, Jan 9, 2009 at 10:33 PM, Scott Lambdin wrote:
> I found a file in rejects, but it may be partial. It gives us some
> information, though.
>
I found a file in rejects, but it may be partial. It gives us some
information, though.
The pgp file was 406184088 bytes and unencrypted is 175246253 bytes.
gpg -v -v -o a_file.out -d a_file.pgp
gpg: armor: BEGIN PGP MESSAGE
gpg: armor header: Version: McAfee E-Business Server v7.5 - Full Licen
Dunno how likely it is, but maybe someone made an attempt at hiding
the size of the file in transit via appending arbitrary data.
2009/1/10 Scott Lambdin :
> Hello -
>
> Someone sends us a big ~700MB pgp encrypted file and when we decrypt it the
> resulting file is about half that size. Anyone ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Scott Lambdin escribió:
...
> To get a still encrypted file, I would have to file a request to modify
> a script and at least 3 groups would have to approve the request. And I
> would have to wait at least 1 week before I actually made the change.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If it is that questionable for anyone, you can always refer them back
to the homepage to get the original source.
http://www.jabberwocky.com/software/paperkey/
Allen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: http://getfi
On Friday 09 January 2009 07:02:52 Werner Koch wrote:
> On Fri, 9 Jan 2009 00:37, cpoll...@embarqmail.com said:
> > What would cause this to be displayed in the log? My secret key has been
> > imported and I can sign messages. After signing a message this error
> > disappears. Any idea what is cau
David Shaw wrote:
> Not double. By definition ASCII armor is around 1/3 larger (actually
> 137%) than the original document (not counting headers and such, but
> they only amount to a few hundred bytes, not megs).
I was assuming that "about double" was a term of art, and it was perhaps
possible t
On Fri, Jan 09, 2009 at 05:05:50PM -0300, Faramir wrote:
> Hello!
> I while ago, there was some talk about Paperkey, and John Clizbe
> was very kind and sent me the binary file compiled for ms-windows.
> Today, in other list, I saw a question about "what about windows users?"
> and paperkey,
It looks like all digits and capital letters. And some kind of spaces or
tabs. It's not a bomb. These file come in routinely. All the ones I have
looked at (ftp'd size vs the unencrypted file sitting in archive) are right
about 2-to-1.
To get a still encrypted file, I would have to file a req
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Scott Lambdin escribió:
> Thanks for the offer but I would be put in Guantanamo bay if I did
> that. ^_^
LOL... well, maybe you could ask the sender to send some harmless file
to you, in order to check if the problem happens again...
Best Rega
On Jan 9, 2009, at 7:07 PM, Robert J. Hansen wrote:
Scott Lambdin wrote:
Someone sends us a big ~700MB pgp encrypted file and when we
decrypt it
the resulting file is about half that size. Anyone have an idea what
they might be doing to swell it up like that?
Option 1: they're not using co
Scott Lambdin wrote:
> Someone sends us a big ~700MB pgp encrypted file and when we decrypt it
> the resulting file is about half that size. Anyone have an idea what
> they might be doing to swell it up like that?
Option 1: they're not using compression and they're ASCII-armoring the
file. You c
Faramir wrote:
> If I understood the license the right way, I can send it, as long as
> I include the source code...
Not quite. The GPL doesn't require you to give source with the binary.
It just requires that if you give someone a binary, you make sure they
know they can also get the source fro
John Clizbe wrote:
> Pleaser take it completely private or Paul add the list to your replies.
Bizarre; his emails to me are showing up as being cc'd to the list.
Perhaps he's not a subscriber, and thus his emails to the list are being
held pending moderation?
If this is the case, Paul, it will do
--armor option swells it up some but doesn't double it.
gpg -r B00BFACE --armor -e -z 0 vshell2.txt
43261322 Mar 6 2008 vshell2.txt
58583901 Jan 9 14:40 vshell2.txt.asc
On Fri, Jan 9, 2009 at 5:36 PM, Scott Lambdin wrote:
> Yes, even with compression disabled, my test files were about the
Yes, even with compression disabled, my test files were about the same size
encrypted or not.
Oh! armored? will test.
On Fri, Jan 9, 2009 at 5:15 PM, Faramir wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello!
>
> Scott Lambdin escribió:
> ...
> > Someone sends us a big ~70
Thanks for the offer but I would be put in Guantanamo bay if I did that.
^_^
On Fri, Jan 9, 2009 at 5:45 PM, David Shaw wrote:
> On Fri, Jan 09, 2009 at 03:33:05PM -0500, Scott Lambdin wrote:
> > Hello -
> >
> > Someone sends us a big ~700MB pgp encrypted file and when we decrypt it
> the
> > r
On Fri, Jan 09, 2009 at 03:33:05PM -0500, Scott Lambdin wrote:
> Hello -
>
> Someone sends us a big ~700MB pgp encrypted file and when we decrypt it the
> resulting file is about half that size. Anyone have an idea what they might
> be doing to swell it up like that?
Most OpenPGP programs compre
On 9 Jan 2009 at 19:15, Faramir wrote:
> Hello!
>
> Scott Lambdin escribió:
> ...
> > Someone sends us a big ~700MB pgp encrypted file and when we decrypt
> > it the resulting file is about half that size. Anyone have an idea
> > what they might be doing to swell it up like that?
>
> That sou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
Scott Lambdin escribió:
...
> Someone sends us a big ~700MB pgp encrypted file and when we decrypt it
> the resulting file is about half that size. Anyone have an idea what
> they might be doing to swell it up like that?
That sounds weird
Hello -
Someone sends us a big ~700MB pgp encrypted file and when we decrypt it the
resulting file is about half that size. Anyone have an idea what they might
be doing to swell it up like that?
--
There's a box?
___
Gnupg-users mailing list
Gnupg-use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello!
I while ago, there was some talk about Paperkey, and John Clizbe
was very kind and sent me the binary file compiled for ms-windows.
Today, in other list, I saw a question about "what about windows users?"
and paperkey, so, I wanted to as
Robert J. Hansen wrote:
> Strenger, Paul V. wrote:
>> 1. What version of GnuPG are you using?
>> gnupg-w32cli-1.2.3
>
> This version is very old and has some known security problems.
> Upgrading to 1.4.9 is definitely recommended.
>
> ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32cli-1.4
Strenger, Paul V. wrote:
> 1. What version of GnuPG are you using?
> gnupg-w32cli-1.2.3
This version is very old and has some known security problems.
Upgrading to 1.4.9 is definitely recommended.
ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32cli-1.4.9.exe
The error message you've at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
jakse escribió:
> Does'nt look good ! i dont have secring.gpg but i doo have one called
> secring.asc
While I can't be sure about that, it looks VERY good...
> does that help me?
*I think* there is a good chance it is what you need. GnuPG uses
Strenger, Paul V. wrote:
> My mistake, it is GNU Privacy Guard (GPG) and not PGP. Let me know if
> you can still assist.
We need to know a lot more details. Let's start with:
1. What version of GnuPG are you using?
2. From where did you get it?
3. What errors are you getting?
4. Does it work
On Fri, 9 Jan 2009 00:37, cpoll...@embarqmail.com said:
> What would cause this to be displayed in the log? My secret key has been
> imported and I can sign messages. After signing a message this error
> disappears. Any idea what is causing this?
There is a gpg-agent command HAVEKEY which is us
Strenger, Paul V. wrote:
> Hello, we are creating a new VM Windows 2003 server and are trying
> to mirror it like our old VM Windows 2000 VM server. We are currently
> running Active Perl 5.8 to use for our PGP Encryption processes and the
> encryption is not working properly on the new machine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
jakse wrote:
> Does'nt look good ! i dont have secring.gpg but i doo have one called
> secring.asc
Try Importing secring.asc into GPG.
JOHN ;)
Timestamp: Friday 09 Jan 2009, 07:37 --500 (Eastern Standard Time)
-BEGIN PGP SIGNATURE-
Version
Hello!
We are pleased to announce version 1.0.5 of Libksba.
Libksba is an X.509 and CMS (PKCS#7) library. It is for example
required to build the S/MIME part of GnuPG-2 (gpgsm). The only build
requirement for Libksba itself is the libgpg-error package. There are
no other dependencies; actual c
Hi!
The key used to sign GnuPG releases expired at the end of last year.
The original plan was to create a new key using a 2048 bit RSA capable
smartcard. However those smartcards will become generally available
only in a few months months and I need to crank out new releases
earlier. Thus I dec
Hello, we are creating a new VM Windows 2003 server and are trying
to mirror it like our old VM Windows 2000 VM server. We are currently
running Active Perl 5.8 to use for our PGP Encryption processes and the
encryption is not working properly on the new machine. We downloaded the
version from
Does'nt look good ! i dont have secring.gpg but i doo have one called
secring.asc
does that help me?
Thanks for the answers!
Faramir-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> jakse escribió:
>> dear forum.
>>
>> I am using GnuPG on my mac. had a problem and had to
35 matches
Mail list logo
