-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 28.08.2006, at 13:32, Alphax wrote:
Simon Ruderich wrote:
Enigmail gave me
gpg: unexpected armor: -BEGIN PGP SIGNED MESSAGE-\n
gpg: invalid radix64 character 3A skipped
gpg: CRC error; 31D9CE - A8932B
gpg: [don't know]: invali
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> On 08/29/2006 04:36 PM, [EMAIL PROTECTED] wrote:
> > Your talking about document inbound to my process, encrypted by the
other
> > organizations. That should work without an issue as you pointed out,
but
> > what about the outbound proces
"Robert J. Hansen" <[EMAIL PROTECTED]> wrote:
> Philipp Gühring wrote:
> > Are there any facts or reasons against CISSP? Are there any
> > alternatives?
>
> Many. Google for "CISSP criticisms" and you'll find a lot of reasons to
> suspect the CISSP, along with some well-regarded alternatives
On Mon, Aug 28, 2006 at 03:22:23PM -0500, [EMAIL PROTECTED] wrote:
>
> I have been working on a process to encrypt data files and send it to other
> organizations for processing. As part of this process, we decided to set
> our key to expire every year. Last year we did not act before the key
>
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 08/29/2006 05:42 PM, [EMAIL PROTECTED] wrote:
[..snip..]
>> This is a rather strange statement.
>> Other organizations should have their OWN pubkeys to which documents
>> sent to them are encrypted.
> Good Point. I wasn't thinking of that. So
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 08/29/2006 04:36 PM, [EMAIL PROTECTED] wrote:
> Your talking about document inbound to my process, encrypted by the other
> organizations. That should work without an issue as you pointed out, but
> what about the outbound process? In that in
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 08/29/2006 04:33 PM, [EMAIL PROTECTED] wrote:
> How do you encrypt to both subkeys? Is this an option turned on with the
> GPG command, or does it mean actually running the input file through two
> seperate GPG commands?
- From gpg manpage:
gp
> On Mon, 2006-08-28 at 15:22 -0500, [EMAIL PROTECTED] wrote:
>
> > I have two questions regarding how to "renew" this key.
> > 1) Is the correct way to renew the key to add another subkey that
expires
> > in September, 2007, or is there a better way?
>
> I do not know of a better way, so my answe
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> On 08/28/2006 10:22 PM, [EMAIL PROTECTED] wrote:
> > I have two questions regarding how to "renew" this key.
> > 1) Is the correct way to renew the key to add another subkey that
expires
> > in September, 2007, or is there a better way?
>
Hi Johan,
Thank you for the suggestion. I do not have any space in between passpharse
and pipe sign and my passphrase does not contain any newline/return.
Thank you.
Bharat.
Johan Wevers wrote:
>
> BharatG wrote:
>
>>type passphrase | gpg --passphrase-fd 0 --decypt-file "File Name"
>>in my case
A key is valid in a keyring once it's signed by an ultimately trusted
key for that keyring, or when it gets enough signatures from other fully
or marginally trusted keys in the ring (this requirement depends on your
configuration, by default one fully trusted key or three marginals make
a key valid
On Mon, 2006-08-28 at 15:22 -0500, [EMAIL PROTECTED] wrote:
> I have two questions regarding how to "renew" this key.
> 1) Is the correct way to renew the key to add another subkey that expires
> in September, 2007, or is there a better way?
I do not know of a better way, so my answer would be ye
12 matches
Mail list logo
