Re: [ANNOUNCE] new release of the ParrotTalk protocol specification, version 3.7

[Eric Rescorla <[e-mail]>]

Robert,

I took a quick look at this document. To be honest, it's a bit hard to make
sense of. There's quite a bit of code and code-like stuff, abd not very
much text. So, for instance, looking at page 18, I see "sharedKey :=
diffieHellman sharedKeyPadPositiveByteArray", but I don't see definitions
for either diffieHellman or sharedKeyPadPositiveByteArray, so I don't know
how to do this computation. If you would like people to provide opinions on
this document, you will probably need to flesh it out more.

With that said, a preliminary question: can you expand on the ways in which
you believe this protocol to be superior to other Authenticated Key
Agreement protocols that we have already standardized in IETF, such as IKE,
SSH, or TLS?

-Ekr



On Tue, Nov 20, 2018 at 8:37 AM Robert <robert.withers=
[e-mail]> wrote:

> I am unsure why Facebook is considered a violation of what a sensible
> person would reach to, as it is not any sort of phishing scam. I also have
> a github project (https://github.com/CallistoHouseLtd/ParrotTalk) and the
> README.MD should prove descriptive. To satisfy your curiousity regarding
> what ParrotTalk is here is a description.
>
> ParrotTalk is an encrypted connection framework. Currently allowing
> anonymous 2048-bit key negotiation to establish user-provided encryption
> cipher and user-provided encoding and decoding, both through a provided
> SessionAgentMap to a starting SessionAgent server. Please look in the test
> case ThunkHelloWorldTest for building these maps and running a connection
> iwth data passing after encryption is established. There is a 4-way
> negotiation, from ProtocolOffered/Accepted to Go/GoToo. In using RSA 2048
> signature validation and DH 2048 primes to establish the key used within
> the selected Cipher. The Cipher and Encoder are selected by name through
> the negotiation protocol. Currently three Ciphers are selectable, AESede,
> DESede, and DES. There are two encoders tested, asn1der, and Bytes. This
> protocol is described here, in these documents.
>
> The two protocol documents v3.6 and v3.7 are hosted on github:
>
> https://github.com/CallistoHouseLtd/ParrotTalk/blob/master/docs/ParrotTalkFrameDesign-3.7.pdf
>
> and
>
>
> https://github.com/CallistoHouseLtd/ParrotTalk/blob/master/docs/ParrotTalkFrameDesign-3.6.pdf
>
> Here is the IETF draft I wrote up for version 3.6, though not yet updated
> for version 3.7. The slides should suffice:
>
>
>
> https://github.com/CallistoHouseLtd/ParrotTalk/blob/master/docs/draft-withers-parrot-talk-v36-00.pdf
>
> Kindly,
> Robert
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, November 20, 2018 8:44 AM, Ted Lemon <[e-mail]> wrote:
>
> It would help to give enough information about what ParrotTalk is so that
> we know whether it's worth visiting the link.   However, that's moot, since
> it's a facebook link, and no sensible person is going to visit it.
>
> On Tue, Nov 20, 2018 at 1:09 AM Robert <robert.withers=
> [e-mail]> wrote:
>
>> Please read my Facebook post introducing the features of the new version
>> 3.7 protocol of ParrotTalk, now a 5 message handshake, 3 messages like TLS
>> 1.3 and an initial 2 message negotiation to determin which version of the
>> protocol to use. My release of the Squeak/Pharo implementation which is
>> capable of supporting both v3.6 and v3.7 in the same SessionAgent, spawning
>> Sessions with either version, based on the negotiation. The Java version at
>> https://github.com/CallistoHouseLtd/ParrotTalk can only talk v3.6 right
>> now. The interesting feature of the Squeak/Pharo implementation is that it
>> supports version negotiation for either version. Tests are all green.
>>
>> https://www.facebook.com/robert.withers
>>
>> best regards,
>> Robert
>>
>>
>>
>