File: set_user_1.out

package info (click to toggle)
postgresql-set-user 4.1.0-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 296 kB
  • sloc: ansic: 714; sql: 249; makefile: 36; sh: 1
file content (433 lines) | stat: -rw-r--r-- 10,309 bytes parent folder | download | duplicates (2)
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
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
CREATE EXTENSION set_user;
-- Ensure the library is loaded.
LOAD 'set_user';
-- Clean up in case a prior regression run failed
-- First suppress NOTICE messages when users/groups don't exist
SET client_min_messages TO 'warning';
DROP USER IF EXISTS dba, bob, joe, newbs, su;
RESET client_min_messages;
-- Create some users to work with
CREATE USER dba;
CREATE USER bob;
CREATE USER joe;
CREATE ROLE newbs;
CREATE ROLE su NOINHERIT;
-- dba is the role we want to allow to execute set_user()
GRANT EXECUTE ON FUNCTION set_user(text) TO dba;
GRANT EXECUTE ON FUNCTION set_user(text,text) TO dba;
GRANT EXECUTE ON FUNCTION set_user_u(text) TO dba;
GRANT newbs TO bob;
-- joe will be able to escalate without set_user() via su
GRANT su TO joe;
GRANT postgres TO su;
-- test reset_user with no initial set
SELECT reset_user();
 reset_user 
------------
 OK
(1 row)

-- test set_user
SET SESSION AUTHORIZATION dba;
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

SELECT set_user('postgres');
ERROR:  switching to superuser not allowed
HINT:  Use 'set_user_u' to escalate.
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

-- test set_user_u
SET SESSION AUTHORIZATION dba;
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

SELECT set_user_u('postgres');
 set_user_u 
------------
 OK
(1 row)

SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | postgres
(1 row)

-- test multiple successive set_user calls
SELECT set_user('joe'); -- fail
ERROR:  must reset previous user prior to setting again
-- ALTER SYSTEM should fail
ALTER SYSTEM SET wal_level = minimal;
ERROR:  ALTER SYSTEM blocked by set_user config
-- COPY PROGRAM should fail
COPY (select 42) TO PROGRAM 'cat';
ERROR:  COPY PROGRAM blocked by set_user config
-- SET log_statement should fail
SET log_statement = 'none';
ERROR:  "SET log_statement" blocked by set_user config
SET log_statement = DEFAULT;
ERROR:  "SET log_statement" blocked by set_user config
RESET log_statement;
ERROR:  "SET log_statement" blocked by set_user config
BEGIN; SET LOCAL log_statement = 'none'; ABORT;
ERROR:  "SET log_statement" blocked by set_user config
-- set_config() should fail
SELECT set_config('wal_level', 'minimal', false);
ERROR:  "pg_catalog.set_config(pg_catalog.text,pg_catalog.text,boolean)" blocked by set_user
HINT:  Use "SET" syntax instead.
CREATE OR REPLACE FUNCTION backdoor(text, text, boolean) RETURNS BOOL AS 'set_config_by_name' LANGUAGE INTERNAL;
SELECT backdoor('log_statement', 'none', true);
ERROR:  "public.backdoor(pg_catalog.text,pg_catalog.text,boolean)" blocked by set_user
HINT:  Use "SET" syntax instead.
UPDATE pg_settings SET setting = 'none' WHERE name = 'log_statement';
ERROR:  "pg_catalog.set_config(pg_catalog.text,pg_catalog.text,boolean)" blocked by set_user
HINT:  Use "SET" syntax instead.
-- test reset_user
RESET ROLE; -- should fail
ERROR:  "SET/RESET ROLE" blocked by set_user
HINT:  Use "SELECT set_user();" or "SELECT reset_user();" instead.
RESET SESSION AUTHORIZATION; -- should fail
ERROR:  "SET/RESET SESSION AUTHORIZATION" blocked by set_user
HINT:  Use "SELECT set_user();" or "SELECT reset_user();" instead.
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | postgres
(1 row)

SELECT reset_user();  -- succeed
 reset_user 
------------
 OK
(1 row)

-- test set_user and reset_user with token
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

SELECT set_user('bob', 'secret');
 set_user 
----------
 OK
(1 row)

SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | bob
(1 row)

RESET ROLE; -- should fail
ERROR:  "SET/RESET ROLE" blocked by set_user
HINT:  Use "SELECT set_user();" or "SELECT reset_user();" instead.
RESET SESSION AUTHORIZATION; -- should fail
ERROR:  "SET/RESET SESSION AUTHORIZATION" blocked by set_user
HINT:  Use "SELECT set_user();" or "SELECT reset_user();" instead.
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | bob
(1 row)

SELECT reset_user(); -- should fail
ERROR:  reset token required but not provided
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | bob
(1 row)

SELECT reset_user('secret'); -- succeed
 reset_user 
------------
 OK
(1 row)

SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

RESET SESSION AUTHORIZATION;
ALTER SYSTEM SET wal_level = minimal;
COPY (select 42) TO PROGRAM 'cat';
SET log_statement = DEFAULT;
-- test transaction handling
CREATE FUNCTION bail() RETURNS bool AS $$
BEGIN
	RAISE EXCEPTION 'bailing out !';
END;
$$ LANGUAGE plpgsql;
SET SESSION AUTHORIZATION dba;
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

-- bail during set_user_u
SELECT set_user_u('postgres'), bail();
ERROR:  bailing out !
CONTEXT:  PL/pgSQL function bail() line 3 at RAISE
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

SHOW log_statement;
 log_statement 
---------------
 none
(1 row)

SHOW log_line_prefix;
 log_line_prefix 
-----------------
 
(1 row)

-- bail on reset after successful set_user_u
SELECT set_user_u('postgres');
 set_user_u 
------------
 OK
(1 row)

SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | postgres
(1 row)

SHOW log_statement;
 log_statement 
---------------
 all
(1 row)

SHOW log_line_prefix;
 log_line_prefix 
-----------------
 AUDIT: 
(1 row)

SELECT reset_user(), bail();
ERROR:  bailing out !
CONTEXT:  PL/pgSQL function bail() line 3 at RAISE
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | postgres
(1 row)

SHOW log_statement;
 log_statement 
---------------
 all
(1 row)

SHOW log_line_prefix;
 log_line_prefix 
-----------------
 AUDIT: 
(1 row)

SELECT reset_user();
 reset_user 
------------
 OK
(1 row)

-- bail during set_user
SELECT set_user('bob'), bail();
ERROR:  bailing out !
CONTEXT:  PL/pgSQL function bail() line 3 at RAISE
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

SHOW log_statement;
 log_statement 
---------------
 none
(1 row)

SHOW log_line_prefix;
 log_line_prefix 
-----------------
 
(1 row)

-- bail during set_user with token
SELECT set_user('bob', 'secret'), bail();
ERROR:  bailing out !
CONTEXT:  PL/pgSQL function bail() line 3 at RAISE
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | dba
(1 row)

SHOW log_statement;
 log_statement 
---------------
 none
(1 row)

SHOW log_line_prefix;
 log_line_prefix 
-----------------
 
(1 row)

-- bail during reset_user with token
SELECT set_user('bob', 'secret');
 set_user 
----------
 OK
(1 row)

SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | bob
(1 row)

SELECT reset_user('secret'), bail();
ERROR:  bailing out !
CONTEXT:  PL/pgSQL function bail() line 3 at RAISE
SELECT SESSION_USER, CURRENT_USER;
 session_user | current_user 
--------------+--------------
 dba          | bob
(1 row)

SELECT reset_user('secret');
 reset_user 
------------
 OK
(1 row)

RESET SESSION AUTHORIZATION;
-- this is an example of how we might audit existing roles
SET SESSION AUTHORIZATION dba;
SELECT set_user_u('postgres');
 set_user_u 
------------
 OK
(1 row)

SELECT rolname FROM pg_authid WHERE rolsuper and rolcanlogin;
 rolname  
----------
 postgres
(1 row)

CREATE OR REPLACE VIEW roletree AS
WITH RECURSIVE
roltree AS (
  SELECT u.rolname AS rolname,
         u.oid AS roloid,
         u.rolcanlogin,
         u.rolsuper,
         '{}'::name[] AS rolparents,
         NULL::oid AS parent_roloid,
         NULL::name AS parent_rolname
  FROM pg_catalog.pg_authid u
  LEFT JOIN pg_catalog.pg_auth_members m on u.oid = m.member
  LEFT JOIN pg_catalog.pg_authid g on m.roleid = g.oid
  WHERE g.oid IS NULL
  UNION ALL
  SELECT u.rolname AS rolname,
         u.oid AS roloid,
         u.rolcanlogin,
         u.rolsuper,
         t.rolparents || g.rolname AS rolparents,
         g.oid AS parent_roloid,
         g.rolname AS parent_rolname
  FROM pg_catalog.pg_authid u
  JOIN pg_catalog.pg_auth_members m on u.oid = m.member
  JOIN pg_catalog.pg_authid g on m.roleid = g.oid
  JOIN roltree t on t.roloid = g.oid
)
SELECT
  r.rolname,
  r.roloid,
  r.rolcanlogin,
  r.rolsuper,
  r.rolparents
FROM roltree r
ORDER BY 1;
-- this will show unacceptable results
-- since postgres can log in directly and
-- joe can escalate via su to postgres
SELECT
  ro.rolname,
  ro.rolcanlogin,
  ro.rolsuper,
  ro.rolparents
FROM roletree ro
WHERE (ro.rolcanlogin AND ro.rolsuper)
OR
(
    ro.rolcanlogin AND EXISTS
    (
      SELECT TRUE FROM roletree ri
      WHERE ri.rolname = ANY (ro.rolparents)
      AND ri.rolsuper
    )
);
 rolname  | rolcanlogin | rolsuper |  rolparents   
----------+-------------+----------+---------------
 joe      | t           | f        | {postgres,su}
 postgres | t           | t        | {}
(2 rows)

-- here is how we fix the environment
-- running this in a transaction that will be aborted
-- since we don't really want to make the postgres user
-- nologin during regression testing
BEGIN;
REVOKE postgres FROM su;
ALTER USER postgres NOLOGIN;
-- retest, this time successfully
SELECT
  ro.rolname,
  ro.rolcanlogin,
  ro.rolsuper,
  ro.rolparents
FROM roletree ro
WHERE (ro.rolcanlogin AND ro.rolsuper)
OR
(
    ro.rolcanlogin AND EXISTS
    (
      SELECT TRUE FROM roletree ri
      WHERE ri.rolname = ANY (ro.rolparents)
      AND ri.rolsuper
    )
);
 rolname | rolcanlogin | rolsuper | rolparents 
---------+-------------+----------+------------
(0 rows)

-- undo those changes
ABORT;