Udo, On 10 Jul 2014, at 10:44, Udo Schneider <Udo.Schneider@homeaddress.de> wrote:
About this larger project was it developed in Pharo? It /is/ still developed - and it's Pharo all the way down. I removed the last non-Pharo component (stunnel) last week when I succeeded in combining the existing LDAP bindings with Zodiac (SSL was a must due to AD integration).
Nice.
Because we are looking for success stories. I can check. The project is an internal-only webapp at the moment.
It basically a "simple" Seaside, Magritte, Bootstrap and SandstoneDB WebApp at first sight. Behind the scenes there are some integration points with REST Services and AD (thus the need for LDAP(S)) going on.
A success story is an application using Pharo that makes a real difference, that adds value in the (commercial) world. Enterprise software is all about integrations, it is never really "simple" ;-) I wish you a successful continuation of the project ! Sven
Best Regards.
Udo
On 10.07.2014 09:41, stepharo wrote:
super
Thalnks for sharing that with us.
About this larger project was it developed in Pharo? Because we are looking for success stories.
Stef
On 10/7/14 09:00, Udo Schneider wrote:
I just extracted some PBKDF2 code from a bigger project. So if you want to derive keys from an non-optimal source (e.g. user input) or store non-reversible passwords with (tunable) secure salting/hashing then PBKDF2 is your friend.
The blog is here: http://readthesourceluke.blogspot.de/2014/07/pbkdf2-for-pharo.html
The source is on SH: http://smalltalkhub.com/#!/~udos/PBKDF2
Have fun!
CU,
Udo