| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This updates the dates of the sponsorships, and moves to a
different date format based on discussion from PGCA board.
|
|
|
|
|
|
These fields aren't editable anyway, but if we don't do the full
validation we will instead crash if for example the same account
creation form is submitted twice (happens surprisingly often). Now we
will instead show a validation error message.
|
|
Author: Jimmy Angelakos <vyruss@hellug.gr>
Reviewed-by: Daniel Gustafsson <daniel@yesql.se>
Discussion: https://postgr.es/m/8e2b0fbcb7f5ce0b061506f95b211729@hellug.gr
|
|
|
|
This was already done for the majority on signin, but for new accounts
we should do the same.
|
|
It's not always entirely correct, but it's less wrong than 200.
|
|
If login isn't completed in 10 minutes, expire the cookie and require a
start-over.
|
|
During oauth logins we need to store some temporary data related to the
users session. Previously we did this in the django session, but thanks
to AI bots trying millions of logins every day (and never completing the
process) we end up with many abandoned sessions in the db. To work
around this, instead store the temporary data in an encrypted cookie
passed to the browser. Since this cookie can be limited in scope to just
the auth part of the site, the slightly larger cookie size doesn't
matter, and we don't need to store any data at all server-side.
|
|
Instead of prepopulating a GET request that could generate a session,
createa a form with different submit buttons and use that. In the brave
new world of AI bots, nobody cares about robots.txt anymore, so we'd get
hit by a lot of requests specifically for these logins that were then
thrown away because they couldn't log in on the third party site.
|
|
This makes for better readability, and is exactly the same
functionality...
Pointed out by Jacob Champion
|
|
This creates a community auth version 3 (previous one being 2, and 1 is
long gone) trhat uses AES_SIV as the encryption method instead of
regular AES_CBC, and validates the digests on all accounts.
As this gets deployed on servers incrementall, the version has to be
specified in the database record for the site. We could have the site
indicate this itself, but doing it this way seems safer as it will then
just break for any app that accidentally reverts the plugin.
Reviewed by Jacob Champion
|
|
This was removed from actual community auth a very long time ago (in
2013, in commit 78de94d1).
|
|
|
|
|
|
|
|
This is not the prettiest at the moment as the server sponsor page doesn't
include logos, but we are obliged to display the Fastly one in return for the
services they provide. We may want to redesign this page at some point in
the future to group by sponsor and work more cleanly with non-server hosting
sponsors.
|
|
This moves the book added in eb46390e since I only remembered to put
in chronological order after pushing.
|
|
Per request by the author on pgsql-www@.
Reported-by: Sonia Valeja <soniavaleja@gmail.com>
Discussion: https://postgr.es/m/CAJz4NYk03KyOVfw8GXif_2c3f2nmOACbNWBNUy9q5R9kd4mWFA@mail.gmail.com
|
|
|
|
|
|
|
|
* Use /etc/os-release instead of lsb_release
* Update list of distribution releases covere
* Drop i386 and s390x architectures
* Use PG 17 in package name examples
|
|
For some reason, downstream repos had a newer version but we forgot it
in the upstream repo.
|
|
Per discussion on -core and -hackers.
|
|
The Schemaverse website no longer responds, so we don't need to
link to it.
Reported-by: Greg Sabino Mullane <htamfids@gmail.com>
|
|
|
|
The CoC had superfluous language on when a CoCC member could be
removed. Given the language didn't provide additional context on
the process of removal, the language itself is removed.
Signed-off-by: Jonathan S. Katz <jonathan.katz@excoventures.com>
|
|
The table describing platform support for Windows downloads still
had a column for 32-bit Windows platforms which was all empty.
Reviewed-by: Magnus Hagander <magnus@hagander.net>
Discussion: https://postgr.es/m/3F3210DF-1A5B-4E6A-B7E1-50B2D9F4D8AD@yesql.se
|
|
Spotted by Daniel Gustafsson
|
|
Much more can be done to help this page, but it's a start.
Reviewed-by: Daniel Gustafsson and Jonathan Katz
|
|
|
|
The full work will be handled in a subsequent patch, but for now
prepare for the update while finalizing the design.
|
|
|
|
As discussed at the dev meeting in Brussels in January 2025.
|
|
|
|
The Contributors Committee wants to add our contact email to our
governance page and also link to the release notes from the
Contributor profile page. It should make it easier to know how to
contact us.
|
|
|
|
|
|
|
|
Per discussion among moderators
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
