-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* sen_ml(_at_)eccosys(_dot_)com (sen_ml(_at_)eccosys(_dot_)com) [000823 10:49]:
I think the only thing one can do is offer help whenever possible,
and view everything with a critical eye, as well as publishing
information about potential problems, to help lesser skilled users
from getting bitten.
i would hesitate to claim uniqueness ("the only thing"), but w/o too
much further thought, i agree w/ the rest.
Obviously you're right. I should have went more along the lines of "the only
thing I can come up with".
imo, part of "publishing information about potential problems" is to
address such issues in relevant ID/RFC/STDs. so, for starters, i
think we should either create another draft or try to incoporate the
substance of this into an existing document.
A big part in the reason why I registered openpgp.org is that I intend to try
to make it a resource for developers and users alike. One of the things I want
to focus on in addition to such basic things as pointing the visitors at other
resources is to help by providing information on best ways to solve problems,
and pointing out what the problems might be in the first place.
This will range from helping users by suggesting secure ways of avoiding loss
of keyrings (pub and priv) to helping programmers by pointing out issues such
as the bcc problem, and ways to fix it.
I hope noone at the IETF-OpenPGP working group feels offended by me
registering the domain.
Terje
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE5o5fW8HLgLrwmRg0RAtsGAJ97Rh3oznPridWWJ3Qxr5R8Hn4wEACfeUYb
XxLVcmcLRgFGfQZNoIuTiXs=
=ZNpA
-----END PGP SIGNATURE-----