I’m not sure if this is interesting to the wider community - but I’m always
genuinely impressed that we continue to get a good trickle of solutions
submitted to Pharo Exercism - and I’m genuinely impressed that there is a team
of folks who quietly co—help in mentoring students and giving
On Mon 19 Aug 2019 at 20:30, Steve Quezadas wrote:
> I am experimenting with smalltalk. Sometimes a function gets
> deprecated and is crossed out. Is there a "smalltalk way" of finding
> the equivalent replacement function?
>
Hello,
Most of the time the deprecation explains what is the new way
I am experimenting with smalltalk. Sometimes a function gets
deprecated and is crossed out. Is there a "smalltalk way" of finding
the equivalent replacement function?
Hello,
Thanks for these nice words.
i do not think after this one im a qualified developer , I still
have to learn a lot.
Roelof
Op 19-8-2019 om 19:54 schreef Richard Sargent:
On Mon, Aug 19, 2019 at 9:40 AM Roelof Wobben wrote:
> Hello Ben,
>
> I think the purpose of this exercise was to practice expecially things
> like encapsulation and thinking in classes.
>
> So I think it's not a big deal to have a setter and a method to check if
> the passwords are matching.
>
Hello Ben,
I think the purpose of this exercise was to practice expecially
things like encapsulation and thinking in classes.
So I think it's not a big deal to have a setter and a method to
check if the passwords are matching.
Roelof
On Mon, 19 Aug 2019 at 22:19, Roelof Wobben wrote:
> Thanks all for the answers.
>
> As I see it , it impossible to store the password in the bankaccount
> object and make safe code to use it,
> So some one give me a stupid assignment.
>
That would seem to depend on the purpose of the
Thanks all for the answers.
As I see it , it impossible to store the password in the
bankaccount object and make safe code to use it,
So some one give me a stupid assignment.
Roelof
Op 19-8-2019 om 11:38 schreef Diego
Hi Jupiter.
This is always a hard problem, as you state: you want a customer to change
their own password, and also want a customer to be allowed to set a password
that he has lost. You could of course make your server code more resilient, and
demand there is security information provided when
Hi Deigo,
Apologies Roelof for jumping in to your thread. :)
This solves the issue of storing passwords, however, Richard made the case for
malevolent or broken code…
- you not only provide a getter for the
password, but a setter! This means that
malevolent/broken code
The best way to implement a password security is to never store the password,
but only a hashed password. This way, you never can have a security leak for
your passwords: because you don’t have them. And for hashing you use a standard
modern hashing algorithm, so it cannot be easily rolled
11 matches
Mail list logo
