9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] tls and iphones and ios9 (sigh)
Date: Fri, 18 Sep 2015 06:01:30 -0700	[thread overview]
Message-ID: <29fe99829da149fd41023ca72d20141a@brasstown.quanstro.net> (raw)
In-Reply-To: <00ce469417599e7228b4eb1207cba938@felloff.net>

On Fri Sep 18 06:01:44 PDT 2015, cinap_lenrek@felloff.net wrote:
> so you need server side support for what cipher suits and protocol
> versions exactly?
>
> the work has been done in 9front libsec and devtls to support ecdhe
> and dhe and tls 1.2 on the *client* side at least. so you can start
> from there. whats missing is the signing and signature verification
> of the dh parameters.

quite a bit of work that looks good.  thanks.

here are some current differences i've got.  the - is your version.
* i think aes_xts should take u32ints as this is defined in the standard.
the assumption that ulong is 32 bits is suspect.

* sorry for the ignorance, but why do we need ripemd160?


../../../include/libsec.h:396,403 - /mnt/term/sys/include/libsec.h:407,414
  PEMChain*readcertchain(char *filename);

  /* aes_xts.c */
- int aes_xts_encrypt(ulong tweak[], ulong ecb[],  vlong sectorNumber, uchar *input, uchar *output, ulong len) ;
- int aes_xts_decrypt(ulong tweak[], ulong ecb[], vlong sectorNumber, uchar *input, uchar *output, ulong len);
+ int aes_xts_encrypt(u32int tweak[], u32int ecb[],  vlong sectorNumber, uchar *input, uchar *output, usize len) ;
+ int aes_xts_decrypt(u32int tweak[], u32int ecb[], vlong sectorNumber, uchar *input, uchar *output, usize len);

  typedef struct ECpoint{
  	int inf;
../../../include/libsec.h:432,439 - /mnt/term/sys/include/libsec.h:443,448
  void	base58enc(uchar *, char *, int);
  int	base58dec(char *, uchar *, int);

- DigestState*	ripemd160(uchar *, ulong, uchar *, DigestState *);
-
  /*
   * Diffie-Hellman key exchange
   */


- erik



  reply	other threads:[~2015-09-18 13:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 14:33 Steve Simon
2015-09-17 15:42 ` Jeff Sickel
2015-09-17 16:38   ` erik quanstrom
2015-09-17 17:46     ` Skip Tavakkolian
2015-09-17 19:47       ` Jeff Sickel
2015-09-18  2:27         ` erik quanstrom
2015-09-18  8:28           ` Brantley Coile
2015-09-18  9:04             ` hiro
2015-09-18  3:19 ` Andrew Simmons
2015-09-18  9:51   ` Steve Simon
2015-09-18 11:10 ` cinap_lenrek
2015-09-18 13:01   ` erik quanstrom [this message]
2015-09-18 13:32     ` cinap_lenrek

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=29fe99829da149fd41023ca72d20141a@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).