From: "steve(dot)b(at)osfda(dot)org" <steve(dot)b(at)osfda(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: pg_ssl_init
Date: 2020-01-03 06:55:21
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

In May of last year (2019), I set up pg_ssl_init on gitlab:

And announced it on this list:

pg_ssl_init is a set of python3 scripts that configures SSL certificates
to insure SECURE remote pgadmin access. To do so manually is a multistep
process, fraught with many opportunities for a mistake to be made and
numerous hours to be wasted troubleshooting it. It has been tested on
popular Linux distros (debian, Ubuntu...), though it is written to _try_
and work on Windows [But I would need a willing tester to get in touch
to confirm that and fix any compatibility issues for Windows...] It
works great on Debian 10.

For some VERY odd reason, while the stub of the repo was still visible,
the files of the repo stopped appearing on gitlab -but the repo was
marked public (?)

I marked the repo private, saved the settings; then marked it public.
Behold: all the files then reappeared.

I guess gitlab is finding out that it's hard to find good technical help!

If anyone reading these posts referring to pg_ssl_init has any problem
in future accessing that repo, get in touch at the contact page at Should gitlab let us down again, at that juncture I will
figure out another amenable open source code hosting solution that's not

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-01-03 07:24:56 Re: [PATCH] Fix parallel query doc typos
Previous Message Michael Paquier 2020-01-03 06:51:32 Re: Commit fest manager for 2020-01