On Tue, Aug 24, 2010 at 3:55 PM, Ford, Mike wrote:
>> -Original Message-
>> From: Andy McKenzie [mailto:amckenz...@gmail.com]
>> Sent: 24 August 2010 17:24
>> To: php-general@lists.php.net
>> Subject: Re: [PHP] Bitwise NOT operator?
>
>
>> From your example, this would have shown me what I
> -Original Message-
> From: Andy McKenzie [mailto:amckenz...@gmail.com]
> Sent: 24 August 2010 17:24
> To: php-general@lists.php.net
> Subject: Re: [PHP] Bitwise NOT operator?
> From your example, this would have shown me what I needed to know:
>
> "Then taking the value of E_NOTICE...
On Tue, 2010-08-24 at 12:24 -0400, Andy McKenzie wrote:
> On Tue, Aug 24, 2010 at 11:06 AM, Richard Quadling
> wrote:
> > On 20 August 2010 17:00, Andy McKenzie wrote:
> >> Thanks to everyone who responded. I've dealt with binary math
> >> before, but it never occurred to me (and doesn't seem
On Tue, Aug 24, 2010 at 11:06 AM, Richard Quadling wrote:
> On 20 August 2010 17:00, Andy McKenzie wrote:
>> Thanks to everyone who responded. I've dealt with binary math
>> before, but it never occurred to me (and doesn't seem to be anywhere
>> in the document page at php.net!) that it would a
On 20 August 2010 17:00, Andy McKenzie wrote:
> Thanks to everyone who responded. I've dealt with binary math
> before, but it never occurred to me (and doesn't seem to be anywhere
> in the document page at php.net!) that it would automatically pad the
> number I entered.
There is no padding.
2010/8/24 Peter Lind :
> On 24 August 2010 16:25, Jan G.B. wrote:
>> 2010/8/24 Bob McConnell :
>>> From: Peter Lind
>>>
On 24 August 2010 15:43, Gary wrote:
> Jan G.B. wrote:
>
>> The weakness of MD5 is mainly because MD5 collisions are possible.
>> That means, that different
On 24 August 2010 16:25, Jan G.B. wrote:
> 2010/8/24 Bob McConnell :
>> From: Peter Lind
>>
>>> On 24 August 2010 15:43, Gary wrote:
Jan G.B. wrote:
> The weakness of MD5 is mainly because MD5 collisions are possible.
> That means, that different strings can have the same MD5-ha
2010/8/24 Bob McConnell :
> From: Peter Lind
>
>> On 24 August 2010 15:43, Gary wrote:
>>> Jan G.B. wrote:
>>>
The weakness of MD5 is mainly because MD5 collisions are possible.
That means, that different strings can have the same MD5-hash...
>>>
>>> http://en.wikipedia.org/wiki/MD5#cite
From: Peter Lind
> On 24 August 2010 15:43, Gary wrote:
>> Jan G.B. wrote:
>>
>>> The weakness of MD5 is mainly because MD5 collisions are possible.
>>> That means, that different strings can have the same MD5-hash...
>>
>> http://en.wikipedia.org/wiki/MD5#cite_note-1
>
> It's worth noting that
On 24 August 2010 15:43, Gary wrote:
> Jan G.B. wrote:
>
>> The weakness of MD5 is mainly because MD5 collisions are possible.
>> That means, that different strings can have the same MD5-hash...
>
> http://en.wikipedia.org/wiki/MD5#cite_note-1
It's worth noting that that essentially does not touc
One thing I would do, and I have done this in many of my applications:
a) Store the username / password in a database.
b) Encrypt passwords (with a salt) with AES-256 using a key stored in a
file OUTSIDE the document path.
c) Add code to the beginning of the included file to ensure it is
2010/8/18 Daniel P. Brown :
> On Tue, Aug 17, 2010 at 15:19, tedd wrote:
>>
>> Bingo -- that worked.
>>
>> It's interesting that a space is optional between -u and user, but required
>> to be absent between -p and password. Seems not symmetrical to me.
>
> The command I sent was because - as I
2010/8/19 Andre Polykanine :
> Hello Nathan,
>
> Sorry, could you provide any links to read for a security noob?)
> Actually, I know that the md5 is decryptable (there are bases with
> words encrypted in md5), but I thought the SHA1 was secure...
> --
> With best regards from Ukraine,
> Andre
> ---
13 matches
Mail list logo
