Re: Re: Encrypting pg_shadow passwords - Mailing list pgsql-hackers

From Jim Mercer
Subject Re: Re: Encrypting pg_shadow passwords
Date
Msg-id 20010616000458.L15040@reptiles.org
Whole thread Raw
In response to Re: Encrypting pg_shadow passwords  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
Responses Re: Re: Encrypting pg_shadow passwords  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
List pgsql-hackers
On Sat, Jun 16, 2001 at 11:20:30AM +0800, Lincoln Yeoh wrote:
> If you need to use encryption then having _everything_ encrypted is a
> better idea - SSL etc. Those >1GHz CPUs are handy ;).

[ yes, i noted the smiley ]

it is rather unfortunate to see the OSS community buying into the tenents
that allowed microsoft to get world domination based on crap quality
software.

"hardware is cheap" is a falsehood.

some people might be suprised at the number of 486's and Pentium 100's that
are still in active use.

in some places, that is leading edge technology, mostly due to economic
realities.

and in a sense, people who have limited resources can be some of the
most satisfied recipients of OSS efforts.

please, lets not have postgresql turn into an OSS behemoth like Mozilla
or OpenOffice.

i am not opposed to more new features, or even adding support for leading
edge hardware.

but, i think it is important to retain as much backward compatibility as
possible.

as well, features should be able to be turned off such that they don't
overly bloat the code.

FreeBSD 4.3 can still be built on a 486.  i'm sure if someone was patient
enought to wait, it could be built on a 386.

this is because it very rarely drops support for something in its code base,
and it makes most features (in the kernel) optional, to limit bloat.

-- 
[ Jim Mercer        jim@reptiles.org         +1 416 410-5633 ]
[ Now with more and longer words for your reading enjoyment. ]


pgsql-hackers by date:

Previous
From: Alex Pilosov
Date:
Subject: Re: Re: Encrypting pg_shadow passwords
Next
From: Manuel Sugawara
Date:
Subject: Re: postgres dies while doing vacuum analyze