-
Notifications
You must be signed in to change notification settings - Fork 5
/
ChangeLog
169 lines (126 loc) · 7.82 KB
/
ChangeLog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
2023-06-10 - Version 2.0.0
This release adds a major feature called Authentication Failure Ban and
the compatibility with PostgreSQL 16. Upgrade require a PostgreSQL restart
to reload the credcheck library.
- Add "Authentication failure ban" new feature
PostgreSQL doesn't have any mechanism to limit the number of authentication
failure attempt before the user being banned. With the credcheck extension,
after an amount of authentication failure defined by configuration directive
`credcheck.max_auth_failure` the user can be banned and never connect anymore
even if it gives the right password later. This feature requires that the
credcheck extension to be added to to `shared_preload_libraries` configuration
option.
All users authentication failures are registered in shared memory with the
timestamps of when the user have been banned. The authentication failures
history is saved into memory only, that mean that the history is lost at
PostgreSQL restart. I have not seen the interest for the moment to restore
the cache at startup.
The authentication failure cache size is set to 1024 records by default and
can be adjusted using the `credcheck.auth_failure_cache_size` configuration
directive. Change of this GUC require a PostgreSQL restart.
Two settings allow to control the behavior of this feature:
* `credcheck.max_auth_failure`: number of authentication failure allowed
for a user before being banned.
* `credcheck.reset_superuser` : force superuser to not be banned or reset
a banned superuser when set to true.
The default value for the first setting is `0` which means that authentication
failure ban feature is disabled. The default value for the second setting is
`false` which means that `postgres` superuser can be banned.
In case the `postgres` superuser was banned, he can not logged anymore. If
there is no other superuser account that can be used to reset the record of
the banned superuser, set the `credcheck.reset_superuser`configuration directive
to `true` into postgresql.conf file and send the SIGHUP signal to the PostgreSQL
process pid so that it will reread the configuration. Next time the superuser will
try to connect, its authentication failure cache entry will be removed.
- Fix Makefile for PG 16. Thanks to Devrim Gunduz for the report.
- Add missing SQL file for version 1.2.0
2023-05-13 - Version 1.2.0
This release fixes a major bug reported by users since last release:
Fix case where password was wrongly saved in the history after a
VALID UNTIL min/max error. Add a regression test for this case.
Thanks to Tushar Takate for the report.
Upgrade require a PostgreSQL restart to reload the credcheck library.
2023-04-27 - Version 1.1.0
This release fixes some minor issues reported by users since last release
and adds a new custom setting:
- credcheck.password_valid_max to force use of VALID UNTIL clause in
CREATE/ALTER ROLE statements with a maximum number of days. Thanks to
Gabriel Leroux for the feature report.
- Explicitely import unistd.h for unlink() calls. Thanks to Gabriel Leroux
for the report.
2023-04-06 - Version 1.0.0
This release adds a major feature called Password Reuse Policy and
the ability to force the use of an expiration date for a password.
It also prevent PostgreSQL to expose the password in the logs in case
of error and fixes some issues reported by users since the past 6 months.
- Add Password Reuse Policy feature. This implementation use a dedicated
shared memory storage to share the password history between all database.
The module must be loaded by adding credcheck to shared_preload_libraries
in postgresql.conf, because it requires additional shared memory.
This means that a server restart is needed to add or remove the module.
When credcheck is active, it stores password history across all databases
of the server. To access and manipulate this history, the module provides a
view pg_password_history and the utility functions pg_password_history_reset()
and pg_password_history_timestamp(). These are not available globally but can
be enabled for a specific database with CREATE EXTENSION credcheck.
The password history is stored in share memory and written to disk in
file $PGDATA/global/pg_password_history to be loaded at startup. The
share memory history size is set to 65535 records by default and can
be adjusted using the credcheck.history_max_size configuration
directive. Change of this GUC require a PostgreSQL restart. One record
in the history takes 144 bytes so the default is to allocate around
10 MB of additional shared memory for the password history.
Two settings allow to control the behavior of this feature:
- credcheck.password_reuse_history: number of distinct passwords set
before a password can be reused.
- credcheck.password_reuse_interval: amount of time it takes before a
password can be reused again.
The default value for these settings are 0 which means that all password
reuse policies are disabled.
The password history consists of passwords a user has been assigned in
the past. credcheck can restrict new passwords from being chosen from
this history:
- If an account is restricted on the basis of number of password changes,
a new password cannot be chosen from the password_reuse_history most
recent passwords. For example, minimum number of password changes is
set to 3, a new password cannot be the same as any of the most recent
3 passwords.
- If an account is restricted based on time elapsed, a new password can't
be chosen from those in the history that are newer than the number of
day set to password_reuse_interval. For example, if the password reuse
interval is set to 365, new password must not be among those previously
chosen within the last year.
Thanks to Umair Shahid and Gabi201265 for the feature request.
- Force PostgreSQL to not expose the password in the log when an error
in CREATE/ALTER role occurs. This behavior can be disabled by setting
the custom variable credcheck.no_password_logging to off.
- Add possibility to enforce the use of an expiration date for a password
with a life time of a specific number of days. Ex:
credcheck.password_valid_until = 60
the password life time must be at least of two months.
Thanks to Umair Shahid for the feature request.
- Allow credcheck to check the user name in CREATE USER statement without
option PASSWORD. Thanks to freeDev84 for the feature report.
- Force credcheck settings to be set/changed only by a superuser.
This fix will break backward compatibility if you use SET credcheck.* on
a non superuser connection.
- Fix detection of the VALID UNTIL clause in CREATE ROLE. Thanks to did16 for
the report.
- Use errcode ERRCODE_INVALID_AUTHORIZATION_SPECIFICATION (28000) for most error messages.
2021-09-20 - Version 0.2.0
This release adds support to PostgreSQL v14 and fix some minor issues
reported by users since the last 3 months.
- Remove SQL extension file as it is empty and not required.
- Fix compilation error with PostgreSQL v14, thanks to Devrim Gunduz
for the report. [ patch from Gilles Darold ]
- Add upgrade SQL script for extension. [ patch from Gilles Darold ]
- Ignore char repeat checks, if the string size is 1
also changing the comment style. [ patch from Dinesh Kumar ]
- Adding file header content. [ patch from Dinesh Kumar ]
- Typo fix in docs. [ patch from Dinesh Kumar ]
2021-06-25 - Version 0.1.1
This release adds minor fixes to ignore char repeat checks if the string
size is 1 and also change the comment style in C code.
2021-06-24 - Version 0.1.0
This is the first release of credcheck extension, which is a credential
checker for the PostgreSQL users.