Neil Conway [EMAIL PROTECTED] writes:
Christopher Kings-Lynne said:
There have been HEAPS of security fixes between 7.2 and 7.3.
That's only the case if your definition of a security fix is pretty fast
and loose -- as yours seems to be.
Hmm? On 7.2, an unpriviliged database user can read
Palle Girgensohn [EMAIL PROTECTED] writes:
One of the reasons I ask is, if it is a good reason, like say
security, maybe I can persuade the FreeBSD port responsible guys to
bring the port into the upcoming FreeBSD 5.0 release.
7.3 is not completely compatible with 7.2 at the SQL level, and
Florian Weimer wrote:
Neil Conway [EMAIL PROTECTED] writes:
Christopher Kings-Lynne said:
There have been HEAPS of security fixes between 7.2 and 7.3.
That's only the case if your definition of a security fix is pretty fast
and loose -- as yours seems to be.
Hmm? On 7.2, an
Bruce Momjian [EMAIL PROTECTED] writes:
Hmm? On 7.2, an unpriviliged database user can read the more or less
the whole memory image of the server process. On 7.3, this has been
fixed.
Huh. Never heard that before.
It's the cash_out(2) crash, but with some other conversion function:
Between 7.2 and 7.3 there was an API change to the pgnotify(?)
struct or something. When 7.3 was released, we forgot to bump the
version number, so we're doing it now. It was something of an
oversight, but it really needed to be done.
There have been HEAPS of security fixes between 7.2
On Mon, 30 Dec 2002, Palle Girgensohn wrote:
One of the reasons I ask is, if it is a good reason, like say security,
maybe I can persuade the FreeBSD port responsible guys to bring the port
into the upcoming FreeBSD 5.0 release. The port freeze was introduced just
before pg-7.3 was released,
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
Since going from 7.2 to 7.3 is a significant upgrade, the FreeBSD guys would
probablyu be right tho to refuse such a major upgrade... Still, it's a pity
though. Postgres 7.3 has been tested and works fine on FreeBSD 5.
FreeBSD uses
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
I forgot one other possible answer: perhaps the port maintainer is taking
a well deserved holiday?
---(end of broadcast)---
--On måndag, december 30, 2002 06.35.22 -0500 Dan Langille
[EMAIL PROTECTED] wrote:
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
I forgot one other possible answer: perhaps the port maintainer is taking
a well
On Mon, 30 Dec 2002, Palle Girgensohn wrote:
--On måndag, december 30, 2002 06.35.22 -0500 Dan Langille
[EMAIL PROTECTED] wrote:
On Mon, 30 Dec 2002, Christopher Kings-Lynne wrote:
ps. Why is Postgres 7.3 still in ports/databases/postgresql-devel ??
I forgot one other possible
Christopher Kings-Lynne said:
There have been HEAPS of security fixes between 7.2 and 7.3.
That's only the case if your definition of a security fix is pretty fast
and loose -- as yours seems to be.
Depending
on your definition of security. eg. Going 'select cash_out(2);' on any
7.2 server
Hi Palle,
Between 7.2 and 7.3 there was an API change to the pgnotify(?) struct or
something. When 7.3 was released, we forgot to bump the version number, so
we're doing it now. It was something of an oversight, but it really needed
to be done.
There have been HEAPS of security fixes between
12 matches
Mail list logo
