Hi Bill,
Well, it depends. How much security do people need. In the NNTP case, I
can't see a strong argument for confidentiality. There may be a need for
compression, which is why I suggested a "TLC" (Transport Level
Compression) facility, which is, to the extent possible, API compatible
with a
Hi Yoav,
And you don’t usually need 25 Mbps for NNTP, although the last time
I actually used NNTP was over a 56Kbps modem.
Yep, accessing text-only newsgroups is fine with a 56Kbps modem, though
getting overview data (roughly the headers of the articles) may take
time on the "subscription" t
On Thu, 2015-09-24 at 18:26 +0300, Ilari Liusvaara wrote:
> On Thu, Sep 24, 2015 at 04:03:28PM +0200, Nikos Mavrogiannopoulos
> wrote:
> > On Thu, 2015-09-24 at 15:27 +0300, Ilari Liusvaara wrote:
> >
> > > 4) For TLS PoP signatures, does it make sense to use HashEdDSA at
> > > all?
> > > Another
On Thu, Sep 24, 2015 at 04:03:28PM +0200, Nikos Mavrogiannopoulos wrote:
> On Thu, 2015-09-24 at 15:27 +0300, Ilari Liusvaara wrote:
>
> > 4) For TLS PoP signatures, does it make sense to use HashEdDSA at
> > all?
> > Another way would to always use PureEdDSA and perform hash separtion
> > from TL
Just in case you’re not on the IETF discuss list.
spt
Begin forwarded message:
> From: NomCom Chair 2015
> Subject: Nomcom 2015: Third and FINAL call for nominations
> Date: September 24, 2015 at 08:29:06 EDT
> To: "IETF Announcement List"
> Reply-To: i...@ietf.org
>
> This is the THIRD call
>> ## Data transfer limitation per connection (issue 125/4)
>>
>> After quibbling with the math a bit, we need to specify how good we
>> think the current ciphers are numbers.
>
> Parse error. Does this mean something like "how much data current
> ciphers can safely encrypt”?
It does. I’ll upd
For this reason (among others) I am against PureEdDSA. HashEdDSA dooes the job
well enough.
Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network.
Original Message
From: Nikos Mavrogiannopoulos
Sent: Thursday, September 24, 2015 10:04
To: Ilari Liusvaara; Simon Josefs
On Thu, 2015-09-24 at 15:27 +0300, Ilari Liusvaara wrote:
> 4) For TLS PoP signatures, does it make sense to use HashEdDSA at
> all?
> Another way would to always use PureEdDSA and perform hash separtion
> from TLS side (e.g. sign(privkey, hash_func_id|H(tbs_data))).
> The certificate signatures a
On Wed, Sep 23, 2015 at 10:33:29AM +0200, Simon Josefsson wrote:
> Hi all,
>
> I have pushed out a new version of the document describing EdDSA public
> keys, signatures and certificates for PKIX. The change in -03 include
> the addition of the prehash mode, test vectors generated by GnuTLS, and
On Thu, 2015-09-24 at 10:52 +0300, Yoav Nir wrote:
> > On other lists I still see the occasional quip about suffering a
> > low
> > bandwidth connection. It used to be folks in some European
> > countries,
> > but most recently I seem to recall South American. (I think we're
> > seeing the shift b
On Thu, 2015-09-24 at 13:23 +1000, Manger, James wrote:
> The cert's notBefore field is a UTCTime value (2-digit year), while
> the notAfter field is a GeneralizedTime value (4-digit year). I don't
> think I has seen that before, but it is valid.
Hi,
Thanks for the comments, they should be addre
"Manger, James" writes:
> Hi Simon, two technical typos:
>
> The example cert in 8.2 has the wrong OID for the signature.
> Cert has { 1 3 101 100 1 } [encoding 06 04 2B656401]
> Text has { 1 3 101 101 } [encoding 06 03 2B6565] for id-EdDSASignature
Hi James. Good catch -- I believe that is
> On Sep 24, 2015, at 7:40 AM, Jeffrey Walton wrote:
>
>> I have to wonder if it’s worth it. In the last decade bandwidth has
>> increased and prices for networking have gone down much faster than CPU
>> speeds. 10 years ago having 1 Mbps at home was the highest-end broadband
>> you could ge
13 matches
Mail list logo
