On Tue, Jun 2, 2020 at 6:18 AM Norbert Hartl <norb...@hartl.name> wrote:
> Hi Paul, > > thanks for the info but I won't read it. I try to focus on things that > matter. There are too many things that try to distract everyone from > producing something helpful. Law suits are IMHO not of that kind. > > I would rather put some money on the table for someone building proper FFI > to openssl. The Cryptography was a mess I cleaned a bit but I had also > scenarios where the squeak code was not working properly. And there is no > real reason to have a smalltalk implementation of crypto if we carry around > openssl anyway (for iceberg and secure connects). > > PierceNg has an implementation that implements a subset of openssl. This > implementation is modeled after the library so lots of class methods. I'd > prefer to have something more object model like. > > So if you think you can implement this please contact me and tell me what > you think how long it takes and how much it will cost to do at least the > things we have now in Cryptography. I'm willing to collect money or pay it > myself. > > I second this. VA Smalltalk included a complete FFI wrapper of OpenSSL in VAST 8.6.2 (2015) and it was one of the best decisions ever. -- Mariano Martinez Peck Email: marianop...@gmail.com Twitter: @MartinezPeck LinkedIn: www.linkedin.com/in/mariano-martinez-peck <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> Blog: https://marianopeck.wordpress.com/
