Le samedi 19 septembre 2009, David Fetter a écrit :
> Folks,
>
> Here's what came out for Mozilla, which, I hope you'll pardon my
> saying so, is a teensy tad more widely used than PostgreSQL has any
> plans to become.
>
> http://www.internetnews.com/government/article.php/3839831/Mozilla+Firefox
On Fri, 2009-09-18 at 18:14 -0700, David Fetter wrote:
> Here's what came out for Mozilla, which, I hope you'll pardon my
> saying so, is a teensy tad more widely used than PostgreSQL has any
> plans to become.
>
> http://www.internetnews.com/government/article.php/3839831/Mozilla+Firefox+Cleared+
On the subject of crypto law - the laws have relaxed significantly in
the last decade to the point where it is now generally safe to export
symmetric encryption up to 128 bits (example: AES), and assymetric
encryption up to 1024 bits (example: RSA). Many countries still require
some sort of lic
David Fetter wrote:
As for the suggestion that we should put other crypto functions into
the core, AIUI the reason not to is not to avoid problems with US
Export Regulations (after all, we've shipped source tarballs with
it for many years, including from US repositories), but to make it
easie
sql-es.org/
- Mensaje original -
De: "Tom Lane"
Para: "David Fetter"
CC: "Andrew Dunstan" , "PG Hackers"
Enviados: Sábado, 19 de Septiembre 2009 6:33:36 GMT -10:00 Hawai
Asunto: Re: [HACKERS] Crypto
David Fetter writes:
> On Sat, Sep 19, 2009 at 11
David Fetter writes:
> On Sat, Sep 19, 2009 at 11:50:35AM -0400, Andrew Dunstan wrote:
>> What benefit would we gain from making general crypto part of the
>> core?
> People may wish to encrypt things in the database.
That is not an argument why it has to be in core rather than an add-on.
On Sat, Sep 19, 2009 at 11:50:35AM -0400, Andrew Dunstan wrote:
>
>
> David Fetter wrote:
>> I suggest that we start by putting secure hashing algorithms into the
>> core distribution so, should MD5 ever break, we have real
>> alternatives, and not done in a panic.
>
> Doing that now would be quite
David Fetter wrote:
I suggest that we start by putting secure hashing algorithms into the
core distribution so, should MD5 ever break, we have real
alternatives, and not done in a panic.
Doing that now would be quite premature. Which algorithm would we choose?
And there is no urgency at
David Do you can comment this altertatives or choices that we have?
We can support us in Bruce Schneier[1], Chief Security Technology Officer, BT
(schne...@schneier.com)
who is one of the person that knows many topics about security in the world. Is
a very nice person and allways is to able to h
