Oh! I was U.N.familiar with Parrot drones. That’s awesome! Well how about using
encrypted communications with a Parrot drone? This is the purpose and
accomplishment of ParrotTalk, encrypted communications.
In 33 classes, minus 4 test classes with 16 tests (same #, 16, as eLinda!),
ParrotTalk delivers 2048-bit key negotiation to encrypt communications with
user-selected (through the SessionAgentMap - see tests) cryptoProtocol [AESede,
DESede, DES], as well as allowing user-selected encoding [asn1der, Bytes
{JSON}] of content data.
I am considering changing the spec to 3.6, as I mentioned.
- HH
On Tue, Oct 24, 2017 at 12:44, Alexandre Bergel
<[[email protected]]("mailto:[email protected]";)> wrote:
> Hi! What ParrotTalk is about? It does not seem related to the drone stuff
> (https://www.parrot.com) ? (Which I first thought). I had a look at the .pdf
> you’ve sent, it seems to do something with networking
> Cheers, Alexandre
>
>> On Oct 24, 2017, at 9:33 AM, henry wrote: > > Hi all, > > I am happy to
>> announce the release of version 3.5 of ParrotTalk, for Squeak and Pharo,
>> found here: > >
>> http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows
>> this specification: >
>> https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFrameDesign-3.5.pdf
>> > > One item of note, in version 3.5, the system connecting to a server,
>> sending the IWant msg, must know the vatId of the system being connected to.
>> I am considering changing this to version 3.6 by removing one round-trip in
>> messaging. Therefore, these messages would be combined: IWant/GiveInfo,
>> IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow
>> eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? >
>> > - HH @callistohouse.club>
