PAPS -ParrotTalk Automated Protocol Selection

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

PAPS -ParrotTalk Automated Protocol Selection

Squeak - Dev mailing list
I have been reworking the initial session stack to use a SessionOperation which does Protocol Selection. Some progress in defining and implementing a new feature of ParrotTalk Automated Protocol Selection - PAPS. Heh.


“With full implementations of SSL (TLS v1.2) [1] and SSH [2] in Squeak’s Cryptography project, a FrameAnalyzer May be able to automatically detect frame specification for a given incoming frame and choose non-ParrotTalk frames and hence distinguish a variety of Protocol SessionOperations (SessionOperations_v3_6, SessionOperations_v3_7, SessionOperations_v3_8, SSL_TLS_1_2, SSL_TLS_v1_3, SSH). That would be a powerful capability.

[1] SSL – http://www.squeaksource.com/Cryptography/SSL-CDavidShaffer.19.mcz

[2] SSH – http://www.squeaksource.com/Cryptography/SSH-rww.12.mcz “

Kindly,
Robert
http://callistohouse.club



Reply | Threaded
Open this post in threaded view
|

Re: PAPS -ParrotTalk Automated Protocol Selection

Squeak - Dev mailing list
  • I ported SSL [1] and SSH [2], onto ParrotTalk's framework, along with a new supporting ParrotTalk [3], including the supporting Telnet [4] and PseudoTTY changesets from Ian Piumarta [5]. Complete delayed credit due to Ian. I harvested the ProtocolState from Ian many, many moons ago and completely forgot to credit him and lost the pointer. Well, in porting Telnet, I rediscovered the original source. I ensured its definition within ParrotTalk, with a few changes I depend on. Thanks Ian!

    I ported initial attempts to subclass an important stateMachine, from each of SSL and SSH, to be rooted at ParrotTalk's SessionOperations. More work is needed, including defining active frameSpecifications that can ddetect appropriate frames for these new Protocols, in a new FrameAnalyzer, to be used by the new SessionProtocolSelector. The current hierarchy of SessionOperations as follows:

    SessionOperations...
  • SessionOperations_v3_8
  • SessionOperations_v3_7
  • SessionOperations_v3_6
  • SSLHandshakeStateMachine
  • SSHTransportHandshakeStateMachine


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 8:00 AM, Robert via Squeak-dev <[hidden email]> wrote:

I have been reworking the initial session stack to use a SessionOperation which does Protocol Selection. Some progress in defining and implementing a new feature of ParrotTalk Automated Protocol Selection - PAPS. Heh.


“With full implementations of SSL (TLS v1.2) [1] and SSH [2] in Squeak’s Cryptography project, a FrameAnalyzer May be able to automatically detect frame specification for a given incoming frame and choose non-ParrotTalk frames and hence distinguish a variety of Protocol SessionOperations (SessionOperations_v3_6, SessionOperations_v3_7, SessionOperations_v3_8, SSL_TLS_1_2, SSL_TLS_v1_3, SSH). That would be a powerful capability.

[1] SSL – http://www.squeaksource.com/Cryptography/SSL-CDavidShaffer.19.mcz

[2] SSH – http://www.squeaksource.com/Cryptography/SSH-rww.12.mcz “

Kindly,
Robert
http://callistohouse.club




Reply | Threaded
Open this post in threaded view
|

Re: PAPS -ParrotTalk Automated Protocol Selection

Squeak - Dev mailing list
I renamed the PaarrotTalk's [3] SessionOperations. The current hierarchy of SessionOperations as follows:

SessionOperations...
- ParrotTalkSessionOperations_v3_8
- ParrotTalkSessionOperations_v3_7
- ParrotTalkSessionOperations_v3_6
- SSLHandshakeStateMachine
- SSHTransportHandshakeStateMachine
Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 9:52 PM, Robert <[hidden email]> wrote:

  • I ported SSL [1] and SSH [2], onto ParrotTalk's framework, along with a new supporting ParrotTalk [3], including the supporting Telnet [4] and PseudoTTY changesets from Ian Piumarta [5]. Complete delayed credit due to Ian. I harvested the ProtocolState from Ian many, many moons ago and completely forgot to credit him and lost the pointer. Well, in porting Telnet, I rediscovered the original source. I ensured its definition within ParrotTalk, with a few changes I depend on. Thanks Ian!

    I ported initial attempts to subclass an important stateMachine, from each of SSL and SSH, to be rooted at ParrotTalk's SessionOperations. More work is needed, including defining active frameSpecifications that can ddetect appropriate frames for these new Protocols, in a new FrameAnalyzer, to be used by the new SessionProtocolSelector. The current hierarchy of SessionOperations as follows:

    SessionOperations...
  • SessionOperations_v3_8
  • SessionOperations_v3_7
  • SessionOperations_v3_6
  • SSLHandshakeStateMachine
  • SSHTransportHandshakeStateMachine


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 8:00 AM, Robert via Squeak-dev <[hidden email]> wrote:

I have been reworking the initial session stack to use a SessionOperation which does Protocol Selection. Some progress in defining and implementing a new feature of ParrotTalk Automated Protocol Selection - PAPS. Heh.


“With full implementations of SSL (TLS v1.2) [1] and SSH [2] in Squeak’s Cryptography project, a FrameAnalyzer May be able to automatically detect frame specification for a given incoming frame and choose non-ParrotTalk frames and hence distinguish a variety of Protocol SessionOperations (SessionOperations_v3_6, SessionOperations_v3_7, SessionOperations_v3_8, SSL_TLS_1_2, SSL_TLS_v1_3, SSH). That would be a powerful capability.

[1] SSL – http://www.squeaksource.com/Cryptography/SSL-CDavidShaffer.19.mcz

[2] SSH – http://www.squeaksource.com/Cryptography/SSH-rww.12.mcz “

Kindly,
Robert
http://callistohouse.club





Reply | Threaded
Open this post in threaded view
|

Re: PAPS -ParrotTalk Automated Protocol Selection

Squeak - Dev mailing list
Some recent posts to my blog regarding ParrotTalk :::

http://callistohouse.club/index.php/2019/06/07/the-logic-behind-parrottalk/

Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 10:02 PM, Robert <[hidden email]> wrote:

I renamed the PaarrotTalk's [3] SessionOperations. The current hierarchy of SessionOperations as follows:

SessionOperations...
- ParrotTalkSessionOperations_v3_8
- ParrotTalkSessionOperations_v3_7
- ParrotTalkSessionOperations_v3_6
- SSLHandshakeStateMachine
- SSHTransportHandshakeStateMachine
Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 9:52 PM, Robert <[hidden email]> wrote:

  • I ported SSL [1] and SSH [2], onto ParrotTalk's framework, along with a new supporting ParrotTalk [3], including the supporting Telnet [4] and PseudoTTY changesets from Ian Piumarta [5]. Complete delayed credit due to Ian. I harvested the ProtocolState from Ian many, many moons ago and completely forgot to credit him and lost the pointer. Well, in porting Telnet, I rediscovered the original source. I ensured its definition within ParrotTalk, with a few changes I depend on. Thanks Ian!

    I ported initial attempts to subclass an important stateMachine, from each of SSL and SSH, to be rooted at ParrotTalk's SessionOperations. More work is needed, including defining active frameSpecifications that can ddetect appropriate frames for these new Protocols, in a new FrameAnalyzer, to be used by the new SessionProtocolSelector. The current hierarchy of SessionOperations as follows:

    SessionOperations...
  • SessionOperations_v3_8
  • SessionOperations_v3_7
  • SessionOperations_v3_6
  • SSLHandshakeStateMachine
  • SSHTransportHandshakeStateMachine


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 8:00 AM, Robert via Squeak-dev <[hidden email]> wrote:

I have been reworking the initial session stack to use a SessionOperation which does Protocol Selection. Some progress in defining and implementing a new feature of ParrotTalk Automated Protocol Selection - PAPS. Heh.


“With full implementations of SSL (TLS v1.2) [1] and SSH [2] in Squeak’s Cryptography project, a FrameAnalyzer May be able to automatically detect frame specification for a given incoming frame and choose non-ParrotTalk frames and hence distinguish a variety of Protocol SessionOperations (SessionOperations_v3_6, SessionOperations_v3_7, SessionOperations_v3_8, SSL_TLS_1_2, SSL_TLS_v1_3, SSH). That would be a powerful capability.

[1] SSL – http://www.squeaksource.com/Cryptography/SSL-CDavidShaffer.19.mcz

[2] SSH – http://www.squeaksource.com/Cryptography/SSH-rww.12.mcz “

Kindly,
Robert
http://callistohouse.club






Reply | Threaded
Open this post in threaded view
|

Re: PAPS -ParrotTalk Automated Protocol Selection

Karl Ramberg

On Sun, Jun 9, 2019 at 4:05 AM Robert via Squeak-dev <[hidden email]> wrote:
Some recent posts to my blog regarding ParrotTalk :::

http://callistohouse.club/index.php/2019/06/07/the-logic-behind-parrottalk/

Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 10:02 PM, Robert <[hidden email]> wrote:

I renamed the PaarrotTalk's [3] SessionOperations. The current hierarchy of SessionOperations as follows:

SessionOperations...
- ParrotTalkSessionOperations_v3_8
- ParrotTalkSessionOperations_v3_7
- ParrotTalkSessionOperations_v3_6
- SSLHandshakeStateMachine
- SSHTransportHandshakeStateMachine
Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 9:52 PM, Robert <[hidden email]> wrote:

  • I ported SSL [1] and SSH [2], onto ParrotTalk's framework, along with a new supporting ParrotTalk [3], including the supporting Telnet [4] and PseudoTTY changesets from Ian Piumarta [5]. Complete delayed credit due to Ian. I harvested the ProtocolState from Ian many, many moons ago and completely forgot to credit him and lost the pointer. Well, in porting Telnet, I rediscovered the original source. I ensured its definition within ParrotTalk, with a few changes I depend on. Thanks Ian!

    I ported initial attempts to subclass an important stateMachine, from each of SSL and SSH, to be rooted at ParrotTalk's SessionOperations. More work is needed, including defining active frameSpecifications that can ddetect appropriate frames for these new Protocols, in a new FrameAnalyzer, to be used by the new SessionProtocolSelector. The current hierarchy of SessionOperations as follows:

    SessionOperations...
  • SessionOperations_v3_8
  • SessionOperations_v3_7
  • SessionOperations_v3_6
  • SSLHandshakeStateMachine
  • SSHTransportHandshakeStateMachine


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 8:00 AM, Robert via Squeak-dev <[hidden email]> wrote:

I have been reworking the initial session stack to use a SessionOperation which does Protocol Selection. Some progress in defining and implementing a new feature of ParrotTalk Automated Protocol Selection - PAPS. Heh.


“With full implementations of SSL (TLS v1.2) [1] and SSH [2] in Squeak’s Cryptography project, a FrameAnalyzer May be able to automatically detect frame specification for a given incoming frame and choose non-ParrotTalk frames and hence distinguish a variety of Protocol SessionOperations (SessionOperations_v3_6, SessionOperations_v3_7, SessionOperations_v3_8, SSL_TLS_1_2, SSL_TLS_v1_3, SSH). That would be a powerful capability.









Reply | Threaded
Open this post in threaded view
|

Re: PAPS -ParrotTalk Automated Protocol Selection

Squeak - Dev mailing list
Yes, I am also having issues. :( I am having to clear my cache of web content, in order to view the blog. Chrome on my iPhone seems to work best. I am in touch with Google Cloud support.

Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, June 9, 2019 6:16 AM, karl ramberg <[hidden email]> wrote:


On Sun, Jun 9, 2019 at 4:05 AM Robert via Squeak-dev <[hidden email]> wrote:
Some recent posts to my blog regarding ParrotTalk :::


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 10:02 PM, Robert <[hidden email]> wrote:

I renamed the PaarrotTalk's [3] SessionOperations. The current hierarchy of SessionOperations as follows:

SessionOperations...
- ParrotTalkSessionOperations_v3_8
- ParrotTalkSessionOperations_v3_7
- ParrotTalkSessionOperations_v3_6
- SSLHandshakeStateMachine
- SSHTransportHandshakeStateMachine
Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 9:52 PM, Robert <[hidden email]> wrote:

  • I ported SSL [1] and SSH [2], onto ParrotTalk's framework, along with a new supporting ParrotTalk [3], including the supporting Telnet [4] and PseudoTTY changesets from Ian Piumarta [5]. Complete delayed credit due to Ian. I harvested the ProtocolState from Ian many, many moons ago and completely forgot to credit him and lost the pointer. Well, in porting Telnet, I rediscovered the original source. I ensured its definition within ParrotTalk, with a few changes I depend on. Thanks Ian!

    I ported initial attempts to subclass an important stateMachine, from each of SSL and SSH, to be rooted at ParrotTalk's SessionOperations. More work is needed, including defining active frameSpecifications that can ddetect appropriate frames for these new Protocols, in a new FrameAnalyzer, to be used by the new SessionProtocolSelector. The current hierarchy of SessionOperations as follows:

    SessionOperations...
  • SessionOperations_v3_8
  • SessionOperations_v3_7
  • SessionOperations_v3_6
  • SSLHandshakeStateMachine
  • SSHTransportHandshakeStateMachine


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 8:00 AM, Robert via Squeak-dev <[hidden email]> wrote:

I have been reworking the initial session stack to use a SessionOperation which does Protocol Selection. Some progress in defining and implementing a new feature of ParrotTalk Automated Protocol Selection - PAPS. Heh.


“With full implementations of SSL (TLS v1.2) [1] and SSH [2] in Squeak’s Cryptography project, a FrameAnalyzer May be able to automatically detect frame specification for a given incoming frame and choose non-ParrotTalk frames and hence distinguish a variety of Protocol SessionOperations (SessionOperations_v3_6, SessionOperations_v3_7, SessionOperations_v3_8, SSL_TLS_1_2, SSL_TLS_v1_3, SSH). That would be a powerful capability.









Reply | Threaded
Open this post in threaded view
|

Re: PAPS -ParrotTalk Automated Protocol Selection

Squeak - Dev mailing list
Alright I got it working. I have been having issues with my browser getting its content cache corrupted resulting in blank pages, and so I figured the issue out. I had installed a URL redirect record in DNS and that was causing the issues. The site should be all fixed now and access to http:///callistohouse.club restored..

Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, June 9, 2019 6:40 AM, Robert via Squeak-dev <[hidden email]> wrote:

Yes, I am also having issues. :( I am having to clear my cache of web content, in order to view the blog. Chrome on my iPhone seems to work best. I am in touch with Google Cloud support.

Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, June 9, 2019 6:16 AM, karl ramberg <[hidden email]> wrote:


On Sun, Jun 9, 2019 at 4:05 AM Robert via Squeak-dev <[hidden email]> wrote:
Some recent posts to my blog regarding ParrotTalk :::


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 10:02 PM, Robert <[hidden email]> wrote:

I renamed the PaarrotTalk's [3] SessionOperations. The current hierarchy of SessionOperations as follows:

SessionOperations...
- ParrotTalkSessionOperations_v3_8
- ParrotTalkSessionOperations_v3_7
- ParrotTalkSessionOperations_v3_6
- SSLHandshakeStateMachine
- SSHTransportHandshakeStateMachine
Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 9:52 PM, Robert <[hidden email]> wrote:

  • I ported SSL [1] and SSH [2], onto ParrotTalk's framework, along with a new supporting ParrotTalk [3], including the supporting Telnet [4] and PseudoTTY changesets from Ian Piumarta [5]. Complete delayed credit due to Ian. I harvested the ProtocolState from Ian many, many moons ago and completely forgot to credit him and lost the pointer. Well, in porting Telnet, I rediscovered the original source. I ensured its definition within ParrotTalk, with a few changes I depend on. Thanks Ian!

    I ported initial attempts to subclass an important stateMachine, from each of SSL and SSH, to be rooted at ParrotTalk's SessionOperations. More work is needed, including defining active frameSpecifications that can ddetect appropriate frames for these new Protocols, in a new FrameAnalyzer, to be used by the new SessionProtocolSelector. The current hierarchy of SessionOperations as follows:

    SessionOperations...
  • SessionOperations_v3_8
  • SessionOperations_v3_7
  • SessionOperations_v3_6
  • SSLHandshakeStateMachine
  • SSHTransportHandshakeStateMachine


Kindly,
Robert


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, June 8, 2019 8:00 AM, Robert via Squeak-dev <[hidden email]> wrote:

I have been reworking the initial session stack to use a SessionOperation which does Protocol Selection. Some progress in defining and implementing a new feature of ParrotTalk Automated Protocol Selection - PAPS. Heh.


“With full implementations of SSL (TLS v1.2) [1] and SSH [2] in Squeak’s Cryptography project, a FrameAnalyzer May be able to automatically detect frame specification for a given incoming frame and choose non-ParrotTalk frames and hence distinguish a variety of Protocol SessionOperations (SessionOperations_v3_6, SessionOperations_v3_7, SessionOperations_v3_8, SSL_TLS_1_2, SSL_TLS_v1_3, SSH). That would be a powerful capability.