Re: [HACKERS] Heads up: upcoming back-branch re-releases
Thanks. Updated. --- Marko Kreen wrote: > +Fix bug in /contrib/pgcrypto Openwall > +gen_salt processing (Marko Kreen> > > I guess it should be bit more explicit: > > Fix bug in /contrib/pgcrypto gen_salt, > which caused it not to use all available salt space for md5 and > xdes algorithms (Marko Kreen, Solar Designer) > Salts for blowfish and standard des are unaffected > > This hopefully makes it clear who is affected and how important is to > upgrade. Also the 'Openwall' is confusing, better credit fix author. > > -- > marko > > ---(end of broadcast)--- > TIP 4: Have you searched our list archives? > >http://archives.postgresql.org > -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [HACKERS] Heads up: upcoming back-branch re-releases
+Fix bug in /contrib/pgcrypto Openwall +gen_salt processing (Marko Kreen> I guess it should be bit more explicit: Fix bug in /contrib/pgcrypto gen_salt, which caused it not to use all available salt space for md5 and xdes algorithms (Marko Kreen, Solar Designer) Salts for blowfish and standard des are unaffected This hopefully makes it clear who is affected and how important is to upgrade. Also the 'Openwall' is confusing, better credit fix author. -- marko ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Heads up: upcoming back-branch re-releases
Kris Jurka <[EMAIL PROTECTED]> writes: > Not a last minute issue or a big deal, but I see no reason for this patch > not to be applied to back branches. > http://archives.postgresql.org/pgsql-patches/2005-12/msg00128.php Well, it hasn't been applied to the *front* branch yet ... but I'll take a look. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] Heads up: upcoming back-branch re-releases
Tom Lane said: > Just FYI, the core committee has agreed we need re-releases to fix the > locale environment issue and other recent bug fixes. Current thought > is to wrap tarballs tomorrow (Thursday) evening, North American eastern > time, with public announcement scheduled for Sunday evening or Monday. > The longer-than-usual interval is because Dave Page and the other > Windows installer team members need a bit of extra time to prepare the > Windows version. > > Any last-minute issues out there? > I have not had time to test the locale fix on Windows, and don't know when I will. Can anyone else help (Magnus maybe?) cheers andrew ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [HACKERS] Heads up: upcoming back-branch re-releases
On Wed, 4 Jan 2006, Tom Lane wrote: Any last-minute issues out there? Not a last minute issue or a big deal, but I see no reason for this patch not to be applied to back branches. http://archives.postgresql.org/pgsql-patches/2005-12/msg00128.php It fixes this problem: http://archives.postgresql.org/pgsql-bugs/2005-12/msg00048.php Kris Jurka ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[HACKERS] Heads up: upcoming back-branch re-releases
Just FYI, the core committee has agreed we need re-releases to fix the locale environment issue and other recent bug fixes. Current thought is to wrap tarballs tomorrow (Thursday) evening, North American eastern time, with public announcement scheduled for Sunday evening or Monday. The longer-than-usual interval is because Dave Page and the other Windows installer team members need a bit of extra time to prepare the Windows version. Any last-minute issues out there? regards, tom lane ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
