|
Home > Archive > Anonymous Servers > June 2005 > GnuPG with JBN and/or Quicksilver
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
GnuPG with JBN and/or Quicksilver
|
|
| nobody@firenze.linux.it 2005-06-21, 5:46 pm |
| This is a Type III anonymous message, sent to you by the Winston Smith
Project mixminion server at firenze.linux.it. If you do not want to
receive anonymous messages, please contact antani-
admin@firenze.linux.it. For more information about anonymity, see
https://remailer.firenze.linux.it or
https://e-privacy.firenze.linux.it.
-----BEGIN TYPE III ANONYMOUS MESSAGE-----
Message-type: plaintext
I realize this is probably a stuipd question but I'll ask anyway.
Has anyone managed to get JBN or Quicksilver to work with GnuPG?
I've got the IDEA dll for gpg and can make and use keys with IDEA.
What else is needed?
-----END TYPE III ANONYMOUS MESSAGE-----
| |
| Italy Anonymous Remailer 2005-06-22, 7:46 am |
| In article <20050621204214.1A83668081@firenze.linux.it>
nobody@firenze.linux.it wrote:
> I realize this is probably a stuipd question but I'll ask anyway.
>
> Has anyone managed to get JBN or Quicksilver to work with GnuPG?
>
> I've got the IDEA dll for gpg and can make and use keys with IDEA.
> What else is needed?
There is no such a thing as stupid questions. Only stupid answers!
I used GnuPG to create nyms with QS. It's a bit tricky, but you have to
export your GnuPG keys and import them to QS's keyring after you set this
option in GPGShell (or use other alternative means to GPGShell):
always-trust
# Create PGP 6.x 7.x compatible keys
#For keys that were generated 'before' this option was used,
#[1] use this option
#[2] change the passphrase on the old keys
#(you can use the exact same passphrase, but now gnupg will protect it
#in a way that is compatible with 6.5.8)
simple-sk-checksum
The # are comments!
JBN does not support GnyPG as I know.
| |
| A.Melon 2005-06-25, 5:46 pm |
| > I used GnuPG to create nyms with QS. It's a bit tricky, but you have to
> export your GnuPG keys and import them to QS's keyring after you set this
> option in GPGShell (or use other alternative means to GPGShell):
>
> always-trust
> # Create PGP 6.x 7.x compatible keys
> #For keys that were generated 'before' this option was used,
> #[1] use this option
> #[2] change the passphrase on the old keys
> #(you can use the exact same passphrase, but now gnupg will protect it
> #in a way that is compatible with 6.5.8)
> simple-sk-checksum
>
> The # are comments!
>
> JBN does not support GnyPG as I know.
>
The instructions you gave do not make QS use GnuPG at all. It
just imports a key created with GnuPG into PGP. QS will still
use PGP to sign, encrypt and decrypt messages. This isn't what
the OP was asking for. They wanted to use GnuPG completely on
it's own without any need to install or use PGP.
| |
| Anonymous 2005-06-25, 5:46 pm |
| > The instructions you gave do not make QS use GnuPG at all. It
> just imports a key created with GnuPG into PGP. QS will still
> use PGP to sign, encrypt and decrypt messages. This isn't what
> the OP was asking for. They wanted to use GnuPG completely on
> it's own without any need to install or use PGP.
I definitely know that it works with the latest *non-beta* QS version.
With the beta version, QS seems to need the PGP key manager to work,
because it doesn't have any more a built-in key manager feature. Having
said that, I have actually made it work with GPGShell!
As far as key *creation* is concerned, I have created GnuPG keys, imported
them to QS, and created nyms with them with no problem using the non-beta
version.
| |
| Thomas J. Boschloo 2005-06-25, 5:46 pm |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Anonymous schreef:
>
>
> I definitely know that it works with the latest *non-beta* QS version.
> With the beta version, QS seems to need the PGP key manager to work,
> because it doesn't have any more a built-in key manager feature. Having
> said that, I have actually made it work with GPGShell!
>
> As far as key *creation* is concerned, I have created GnuPG keys, imported
> them to QS, and created nyms with them with no problem using the non-beta
> version.
That is good to hear! I also want to draw your attention to these four
switches in GnuPG 1.4.1:
- --pgp2 Set up all options to be as PGP 2.x compliant as
possible, and warn if an action is taken (e.g.
encrypting to a non-RSA key) that will create a
message that PGP 2.x will not be able to handle.
Note that `PGP 2.x' here means `MIT PGP 2.6.2'.
There are other versions of PGP 2.x available, but
the MIT release is a good common baseline.
This option implies `--rfc1991 --disable-mdc --no-
force-v4-certs --no-sk-comment --escape-from-lines
--force-v3-sigs --no-ask-sig-expire --no-ask-cert-
expire --cipher-algo IDEA --digest-algo MD5 --com-
press-algo 1'. It also disables --textmode when
encrypting.
- --pgp6 Set up all options to be as PGP 6 compliant as pos-
sible. This restricts you to the ciphers IDEA (if
the IDEA plugin is installed), 3DES, and CAST5, the
hashes MD5, SHA1 and RIPEMD160, and the compression
algorithms none and ZIP. This also disables
--throw-keyids, and making signatures with signing
subkeys as PGP 6 does not understand signatures
made by signing subkeys.
This option implies `--disable-mdc --no-sk-comment
--escape-from-lines --force-v3-sigs --no-ask-sig-
expire'
- --pgp7 Set up all options to be as PGP 7 compliant as pos-
sible. This is identical to --pgp6 except that
MDCs are not disabled, and the list of allowable
ciphers is expanded to add AES128, AES192, AES256,
and TWOFISH.
- --pgp8 Set up all options to be as PGP 8 compliant as pos-
sible. PGP 8 is a lot closer to the OpenPGP stan-
dard than previous versions of PGP, so all this
does is disable --throw-keyids and set --escape-
from-lines. All algorithms are allowed except for
the SHA384 and SHA512 digests.
You can add them to your gpg.conf in the directory where your (gpg)
keyrings also are located. I think QS supports pgp 6, 7 and 8. It is
probably easy to import your current official pgp keys to gnupg, but the
other way around should also work. Seting the passphrase to nothing
first might help export your existing secret keys in a format QS can
use. (haven't tried to do this myself yet)
hth,
Thomas
- --
"You can't be safer, can't be more secure than with a breast in each
palm, that's the way I was born and that's the way I want to die" -
Sugarcubes, Mama, 1988
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQB5AwUBQr3VogEP2l8iXKAJAQJnswMfR8xFUwPP
r3GZTlQY5td1MxHTtDZRqLmB
MxbDAq+Re2QvV5jRnRhwKCxSYaEKlHNBKPz9z1n1
Yr3wtVEjy5TvWPALi5ZmN6L+
XIj2YAF8X/5cXkjxEdoqVbcMUSeWrQgmLjelWQ==
=IKXy
-----END PGP SIGNATURE-----
| |
| Anonymous 2005-06-26, 5:46 pm |
| In <b732354aeb7522c6a1b942cef5bf520c@anon.bananasplit.info>, anonymous@invalid.com wrote:
>
>I definitely know that it works with the latest *non-beta* QS version.
>With the beta version, QS seems to need the PGP key manager to work,
>because it doesn't have any more a built-in key manager feature. Having
>said that, I have actually made it work with GPGShell!
GPGShell with QS Beta Version? Would you care to define the procedure for doing this?
>As far as key *creation* is concerned, I have created GnuPG keys, imported
>them to QS, and created nyms with them with no problem using the non-beta
>version.
-=-
This message was sent via two or more anonymous remailing services.
|
|
|
|
|