Re: Using AES256 cipher directly...?

2018-12-11 Thread Hubert Kario
On Friday, 7 December 2018 18:24:38 CET Paul Smith wrote: > Thanks for your reply Martin! > > On Fri, 2018-12-07 at 10:46 -0500, Martin Thomson wrote: > > Unfortunately, we can't say that we have a PAKE, so I appreciate that > > you aren't able to just drop that in. > > A concern is that I have

Re: Using AES256 cipher directly...?

2018-12-07 Thread Martin Thomson
On Fri, Dec 7, 2018 at 12:26 PM Paul Smith wrote: > Another thing that I didn't bring up: I need to implement this in other > languages (at least Java and Python), so clients can connect to the > service. So I need to consider availability in other crypto libraries > like Python ssl and javax

Re: Using AES256 cipher directly...?

2018-12-07 Thread Paul Smith
Thanks for your reply Martin! On Fri, 2018-12-07 at 10:46 -0500, Martin Thomson wrote: > Unfortunately, we can't say that we have a PAKE, so I appreciate that > you aren't able to just drop that in. A concern is that I have to support full backward-compatibility, not a "flag day" upgrade, so

Re: Using AES256 cipher directly...?

2018-12-07 Thread Martin Thomson
Hi Paul, I think NSS has all you need here. Including TLS 1.3 should you prefer that. Unfortunately, we can't say that we have a PAKE, so I appreciate that you aren't able to just drop that in. In the meantime,,, On Fri, Dec 7, 2018 at 9:18 AM Paul Smith wrote: > I have a session key from

Using AES256 cipher directly...?

2018-12-07 Thread Paul Smith
Hi all. Hopefully this is the right place. I have a system (first created ~8 years ago) based on SRP and RC4 (I know). This system creates TCP connections rarely and uses them for a very long time, and they cannot be dropped/reconnected without user- visible disruption, so it's very different