-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

On 02/01/16, Moderator pondered and said...

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

Would like to restart that conversation. :)

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

Walk me through this Mark, I'm just learning about public/private keys and getting my head around all of this.

So I have installed a gpg4win bundle on my pc and have created a public key which I can post here and you (or others) can then use to encrypt a message
to send to me - right?

But if I were to post and encrypted message here it would be of no use to anyone unless I had encrypted it using someone elses public key (so they
could unlock it) - right?

Best, Paul

--- Mystic BBS v1.12 A4 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

On 02/24/16, mark lewis pondered and said...

have at it :)

Cheers ears.

So I have installed a gpg4win bundle on my pc and have created a public key which I can post here and you (or others) can then use to encrypt a message to send to me - right?

yes... your signature should also end up on one of the public keyring servers so that anyone can retrieve it... the trick is interfacing with FTN software if you want to use it in this environment... the body of
the message, without control lines, has to be saved to a temp file, pgp
or gpg run on it to wrap and sign it and then the temp file gets
imported to replace the original... on my TimED/2 system, i have the following options and commands...

[snip - examples]

Thanks :) Very detailed and looks good for those tools. I'm trying to figure out a way to do something similar with Mystic but at this stage I am unsure
how I could write something on the fly and have it posted encoded or read something encoded as decoded on the fly. It seems I could use the mutil tool
to post a manually created encoded text file with ease to a jam base and I guess I can manually export a message from a jam base to a text file then manually decode it.. it's just all rather labour intensive. :(

But if I were to post and encrypted message here it would be of no us to anyone unless I had encrypted it using someone elses public key (s they could unlock it) - right?

it works two ways...

1. if you post a message encrypted with your PRIVATE key, anyone with
your PUBLIC key can decrypt it... that proves it was you that encrypted it... 2. if you post a message encrypted with my PUBLIC key, only i will be able to decrypt it...

Gotcha..

then there's signing a message instead of encrypting it... signing wraps the message and places a digital signature at the bottom... others use your public key to verify that you really did sign the message *and*
that it hasn't been altered in transit... signing is very common and generally seen in message posting areas... encrypted stuff may be used more in private transactions, though... i'm not sure there is a metric
for counting those...

OK, I will need to look at the tool I have downloaded to see how I could do that, although I am more interested in doing encrypted stuff using an
othernet to test things out as I realise Fidonet policy is not really an enabler of wholesale encrypted traffic :)

we have to make sure that in FTNs, and other places like news groups and mailing lists, that we are having the tool to emit ascii and not
binary... it is possible to encrypt a message and the result is binary which is sent but trying to get binary into a message and get it back
out without altering it is tricky at best... much easier to use ascii which is already formatted and wrapped to 70 characters and ready to
post anywhere...

Yep that's fine the tool I have been playing with does this with ease. I also came to the same conclusions quite quickly as well.

PGP Fingerprint 0xB60C20C5

When I get something sorted over the weekend I will post the same here.

Did you get the netmail I sent you?

Best,Paul

--- Mystic BBS v1.12 A5 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)

-----BEGIN PGP SIGNED MESSAGE-----


Conference rules for the PUBLIC_KEYS echo: rev. 2 JUL 01
Posting Frequency: 1st and 15th of the month.
-----------------------------------------------------------------------

1. The purpose of this echo is to provide a place to discuss
public-keys for data privacy within FidoNet and elsewhere. We also
consider electronic signature possibilities using public-keys and
discuss data and software encryption and the various schemes and
programs that produce them.

This is a companion conference to PKEY_DROP Echo. It is distributed
via the same channels as PKEY_DROP. It is highly suggested that
both echos be made available on systems that carry one or the
other.

2. Stay on-topic. Topics of keys and encryption and related privacy
and electronic signature issues are welcome. Others are not.

3. No politics [except as it relates to privacy issues] and no
religion.

4. No personal attacks, slurs or innuendo. Stick to issues not
personalities.

5. No Private flagged messages in Echomail! Encrypted traffic using
public-keys is permitted for the exercise so long as it is
on-topic. Don't send person-specific encrypted traffic. Such
specific traffic belongs in direct Netmail. Encrypted traffic
should be in the form of ASCII-armored or personal key encrypted
messages that can be read by anyone with PGP 2.6+ and your
public-key. Include your public-key in a separate message before
sending such test messages in case the other end doesn't have it
or make them aware of how to get it from your system. If you just
want to post your public-key, use PKEY_DROP Echo.

6. Clear-signed messages are not encrypted and may be used freely in
this Echo.

7. This Echo may be traveling around the world so try to be concise.
Avoid excessive quoting for one-liner responses.

8. Be aware that Echomail is NOT secure. Don't take anything at face
value.

9. The posts in this Echo are the sole responsiblity of the poster. If
you need verification, use Netmail.

10. The Moderator will deal with off-topic traffic. Don't respond for
him. Links to this Echo will only be curtailed when absolutely
necessary so please don't make it necessary. [grin]

The Moderator is Mark Lewis at 1:3634/12. [KeyID: 0xB60C20C5]
A Moderator Emeritus is Jim Cannell at 1:15/21. [KeyID: 0xB7822B3D]


Mark Lewis, 1:3634/12, wkitty42@alltel.net

Conference Moderators


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Privacy is a right to fight for.

iQCVAwUBO0Dc9psj1FW2DCDFAQEtkgQAqrw7lX4/fIvWFtR0Ym2VjcGLHpDAqieJ /8pBdd1rfHSL+pcKB3HL+31Y6TJp9Cw5VxWol1M4++36Rp1EVjqgZ0K8xR2/sxNp 9YDLtUQVklSbBvYODzVfIQdIaBwgdG8kR5WtuAqkK1OjRAFtr/chJd1jE9g8/T2H
kbmztPm4Ja4=
=XH58
-----END PGP SIGNATURE-----


* Origin: (1:3634/12)