On November 2, 2015 5:29:29 AM GMT+01:00, Ralf Quint
wrote:
>The downside of that approach however is that it this opens up the
>possibility to create a matching hash on "inappropriate" passwords (too
>
>short, easy to look up/guess) and hence get access...
And that's why we use cryptographi
On 11/1/2015 7:50 PM, Anthony Walter wrote:
Ideally you shouldn't store passwords at all. You store the hash to
the password. In this way, someone at your business, or someone with
access to your business, or if someone mistakenly installs some
malicious software, your users passwords can never
Ideally you shouldn't store passwords at all. You store the hash to the
password. In this way, someone at your business, or someone with access to
your business, or if someone mistakenly installs some malicious software,
your users passwords can never be retrieved.
When someone logs into your soft
2015-10-30 10:04 GMT+01:00 Marco van de Voort :
> In our previous episode, Klaus Hartnegg said:
> > With password
> > there would have to be a plan B in case users forget a password.
>
> And now you need a plan B for when the user changes email address.
>
Yes, this is where things could go wrong.
On Sun, 01 Nov 2015 17:25:55 +, Mark Morgan Lloyd
wrote:
>Tobias Giesen wrote:
>> Yes it will terminate and free (if FreeOnTerminate is true).
>
>Remember that if it frees itself due to falling out of the Execute()
>procedure, a variable containing the TThread descendant won't be set nil.
>
Tobias Giesen wrote:
Yes it will terminate and free (if FreeOnTerminate is true).
Remember that if it frees itself due to falling out of the Execute()
procedure, a variable containing the TThread descendant won't be set nil.
On the other hand, if it doesn't free itself and relies on the main
Yes it will terminate and free (if FreeOnTerminate is true).
-
Please excuse the shortness of this mail which was sent from my mobile phone.
If necessary, I will send more information later.
Cheers,
Tobias Giesen
> On 01.11.2015, at 15:25, Bo Berglund wrote:
>
> I have seen that the Exe
I have seen that the Execute method must chect for Terminated in its
loop and exit if Terminated is set to true.
But I cannot find mention on what happens if the Execute method exits
without Terminated having first been set.
Does this cause the thread itself to terminate and free or what
happens?
