Cryptography: plugins

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

Cryptography: plugins

cdavidshaffer
The Cryptography package (at one point) contained the following classes
which extend "plugin" related classes which are not part of the typical
squeak image btw, typical = used by me :-)

DESPlugin (subclass of InterpreterPlugin)
DSAPlugin (subclass of InterpreterPlugin)
MD5Plugin (subclass of SmartSyntaxInterpreterPlugin)

These seem to have been dropped from various forks and the trunk
probably because the publisher (including me) did not have the
appropriate superclasses loaded when we loaded Cryptography.  The latest
versions were available in mtf.13.  So:

1) Are these plugins to be maintained as part of Cryptography? or
somewhere else?
2) If "yes" to 1, can I move them to a separate Monticello package?

David


Reply | Threaded
Open this post in threaded view
|

Re: [Cryptography Team] Cryptography: plugins

Rob Withers

--------------------------------------------------
From: "C. David Shaffer" <[hidden email]>
Sent: Monday, July 05, 2010 4:49 PM
To: "The general-purpose Squeak developers list"
<[hidden email]>; "Squeak Cryptography"
<[hidden email]>
Subject: [Cryptography Team] Cryptography: plugins

> The Cryptography package (at one point) contained the following classes
> which extend "plugin" related classes which are not part of the typical
> squeak image btw, typical = used by me :-)
>
> DESPlugin (subclass of InterpreterPlugin)
> DSAPlugin (subclass of InterpreterPlugin)
> MD5Plugin (subclass of SmartSyntaxInterpreterPlugin)
>
> These seem to have been dropped from various forks and the trunk
> probably because the publisher (including me) did not have the
> appropriate superclasses loaded when we loaded Cryptography.  The latest
> versions were available in mtf.13.  So:
>
> 1) Are these plugins to be maintained as part of Cryptography? or
> somewhere else?
> 2) If "yes" to 1, can I move them to a separate Monticello package?

I think it is a good idea to store these separately from the Cryptography
package.  I believe we made sure that tests run without the plugins, so
Cryptography out of the box, without the plugins, is functional.  We could
have a Cryptography-Plugins package to store these.  Then the challenge is
to get VM builders to load this package when building VMs for distribution.

Nice work.

Rob

>
> David
>
> _______________________________________________
> Cryptography mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography

 


Reply | Threaded
Open this post in threaded view
|

Re: [Cryptography Team] Cryptography: plugins

Levente Uzonyi-2
In reply to this post by cdavidshaffer
On Mon, 5 Jul 2010, C. David Shaffer wrote:

> The Cryptography package (at one point) contained the following classes
> which extend "plugin" related classes which are not part of the typical
> squeak image btw, typical = used by me :-)
>
> DESPlugin (subclass of InterpreterPlugin)
> DSAPlugin (subclass of InterpreterPlugin)
> MD5Plugin (subclass of SmartSyntaxInterpreterPlugin)
>
> These seem to have been dropped from various forks and the trunk
> probably because the publisher (including me) did not have the
> appropriate superclasses loaded when we loaded Cryptography.  The latest
> versions were available in mtf.13.  So:
>
> 1) Are these plugins to be maintained as part of Cryptography? or
> somewhere else?
> 2) If "yes" to 1, can I move them to a separate Monticello package?

The Cryptography package is already oversized, moving the plugin code to a
separate package is definitely a good idea.
Btw, if you're merging forks, consider merging my packages which never
made it to squeaksource: http://leves.web.elte.hu/cryptography/ . Details
are in the log messages and here:
http://lists.squeakfoundation.org/pipermail/cryptography/2008-March/000569.html 

Reply | Threaded
Open this post in threaded view
|

Re: [Cryptography Team] Cryptography: plugins

cdavidshaffer
On 07/05/10 19:45, Levente Uzonyi wrote:
>
> The Cryptography package is already oversized, moving the plugin code
> to a separate package is definitely a good idea.
> Btw, if you're merging forks, consider merging my packages which never
> made it to squeaksource: http://leves.web.elte.hu/cryptography/ .
> Details are in the log messages and here:
> http://lists.squeakfoundation.org/pipermail/cryptography/2008-March/000569.html
> _______________________________________________

I merged your changes and split the Cryptography package.  The current
version of the plugins are untested so if someone wants to have a crack
at running the tests with the plugin versions, that would be helpful.
Thanks!

David


Reply | Threaded
Open this post in threaded view
|

RE: [Cryptography Team] Cryptography: plugins

Ron Teitelbaum
In reply to this post by Levente Uzonyi-2
Hi Levente,

Sorry about that.  I'm glad to see that they were integrated.  Thanks for
doing the work!

All the best,

Ron Teitelbaum

> -----Original Message-----
> From: [hidden email]
> [mailto:[hidden email]] On Behalf Of
> Levente Uzonyi
> Sent: Monday, July 05, 2010 7:45 PM
> To: Cryptography Team Development List
> Cc: The general-purpose Squeak developers list
> Subject: Re: [Cryptography Team] Cryptography: plugins
>
> On Mon, 5 Jul 2010, C. David Shaffer wrote:
>
> > The Cryptography package (at one point) contained the following classes
> > which extend "plugin" related classes which are not part of the typical
> > squeak image btw, typical = used by me :-)
> >
> > DESPlugin (subclass of InterpreterPlugin)
> > DSAPlugin (subclass of InterpreterPlugin)
> > MD5Plugin (subclass of SmartSyntaxInterpreterPlugin)
> >
> > These seem to have been dropped from various forks and the trunk
> > probably because the publisher (including me) did not have the
> > appropriate superclasses loaded when we loaded Cryptography.  The latest
> > versions were available in mtf.13.  So:
> >
> > 1) Are these plugins to be maintained as part of Cryptography? or
> > somewhere else?
> > 2) If "yes" to 1, can I move them to a separate Monticello package?
>
> The Cryptography package is already oversized, moving the plugin code to a
> separate package is definitely a good idea.
> Btw, if you're merging forks, consider merging my packages which never
> made it to squeaksource: http://leves.web.elte.hu/cryptography/ . Details
> are in the log messages and here:
> http://lists.squeakfoundation.org/pipermail/cryptography/2008-
> March/000569.html
> _______________________________________________
> Cryptography mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography