BUG #16056: Actually PGADMIN4

Поиск
Список
Период
Сортировка
От PG Bug reporting form
Тема BUG #16056: Actually PGADMIN4
Дата
Msg-id 16056-ca451f9ab3d3d624@postgresql.org
обсуждение исходный текст
Список pgsql-bugs
The following bug has been logged on the website:

Bug reference:      16056
Logged by:          Paul Kudla
Email address:      paul@scom.ca
PostgreSQL version: 12.0
Operating system:   windows ten
Description:

Unable to stop it from asking for a master password

I have tried
##########################################################################
# Master password is used to encrypt/decrypt saved server passwords
# Applicable for desktop mode only
##########################################################################
MASTER_PASSWORD_REQUIRED = False


in config.py
config_local.py

registery entry carrier no config info contrary to your own documentation.

nothing seems to be supported

Notes about security

I as a programmer am getting frustrated on other programmers or accountants
as i call them adding security measures that really dont need to be
implemented

I run secure networks, gre networks between building etc etc and all this
does is add an extra layer of work

i lost 2 hours messing with this because you prompted me to do an update,
and have given up thus the bug report

PG Admin version is 4.13

Please provide a documentated way to deal with this issue.


В списке pgsql-bugs по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #16045: vacuum_db crash and illegal memory alloc after pg_upgrade from PG11 to PG12
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: BUG #16045: vacuum_db crash and illegal memory alloc afterpg_upgrade from PG11 to PG12