9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spam rejection after reception does have limits
Date: Sun, 28 Sep 2003 11:16:41 +0100	[thread overview]
Message-ID: <37477b39bbe70b4ef8ddcfdb150ea72e@caldo.demon.co.uk> (raw)
In-Reply-To: <020001c3859e$d209f220$b9844051@insultant.net>

>> PS: I don't have a problem with each mail recipient acting as its
>> own CA and issuing certificates left, right and centre that can be
>> used to further certify agents on behalf of the sender.  X.509's
>> certification hierarchy allows for this and it may be best employed
>> as a certification audit trail.

>you don't understand the the faults of PKI.  issuing certs left right and
>center breaks the 'trust'.  paying money to root CA's (which i don't trust)
>is a waste of money and time.

there has been quite a bit of work done and published before and after
x.509 (and PGP as well for that matter).

i recently discovered
http://www.anu.edu.au/people/Roger.Clarke/EC/Bled03.html, which
is quite a good brisk survey, with trenchant observations.

Carl Ellison has a good web site with lots of useful links:
to other good web sites:
http://world.std.com/~cme/html/spki.html.

aside: the parent site has a link that takes a good whack at ASN.1
``ASN.1 is viewed differently by writers of standards and implementers.
Neither group is unanimous in its evaluation, but it tends to be predominantly
favoured by the former and predominantly despised by the latter.''
http://world.std.com/~cme/P1363/asn1.html
``... for a total code size [for ASN.1] of 55085 characters, as compared
to the original 48 characters [for the obvious if less flexible C version] ... an expansion
in code by a factor of 1148''



  parent reply	other threads:[~2003-09-28 10:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27 22:46 ron minnich
2003-09-28  1:11 ` boyd, rounin
2003-09-28  9:08   ` Charles Forsyth
2003-09-28  9:16     ` boyd, rounin
2003-09-28  8:10 ` Lucio De Re
2003-09-28  8:59   ` boyd, rounin
2003-09-28  9:42     ` Lucio De Re
2003-09-28 10:18       ` boyd, rounin
2003-09-28 10:50       ` boyd, rounin
2003-09-28 11:18         ` Lucio De Re
2003-09-28 11:44           ` boyd, rounin
2003-09-28 11:05       ` boyd, rounin
2003-09-28 11:47         ` Lucio De Re
2003-09-28 11:58           ` boyd, rounin
2003-09-28 12:17             ` Lucio De Re
2003-09-29  9:14         ` Douglas A. Gwyn
2003-09-29  9:37           ` boyd
2003-09-28 15:33       ` ron minnich
2003-09-28 15:39         ` boyd, rounin
2003-09-28 17:12           ` ron minnich
2003-09-28 17:22             ` boyd
2003-09-28 10:16     ` Charles Forsyth [this message]
2003-09-28 10:23       ` boyd, rounin
2003-09-29  3:23         ` salomo3
2003-09-29  3:32           ` boyd
2003-09-29  5:18             ` Lucio De Re
2003-09-29  9:18               ` boyd
2003-09-29 13:53             ` Joel Salomon
2003-09-29  9:14     ` Douglas A. Gwyn
2003-09-29  9:13   ` Douglas A. Gwyn
2003-09-29  9:44     ` SPAM: " Charles Forsyth
2003-09-29 15:21       ` Douglas A. Gwyn
2003-09-29 16:02         ` Joel Salomon
2003-09-29 21:24           ` boyd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37477b39bbe70b4ef8ddcfdb150ea72e@caldo.demon.co.uk \
    --to=forsyth@caldo.demon.co.uk \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).