On Tue, 18 Jun 2024 15:42:10 -0500
"David C. Rankin" wrote:
> On 6/18/24 05:35, Carl Lei wrote:
> > Oh, I meant to run another apache instance, serving only the git
> > CGI, and reverse-proxy from your main HTTP server to this dedicated
> > git server. Actually it need not be apache, any kind of
On 6/18/24 05:35, Carl Lei wrote:
Oh, I meant to run another apache instance, serving only the git CGI,
and reverse-proxy from your main HTTP server to this dedicated git
server. Actually it need not be apache, any kind of server capable of
running CGI will do fine.
That I'll have to digest. S
It takes some time to time out.
--
Jude
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.
Please use in that order."
Ed Howdershelt 1940.
On Tue, 18 Jun 2024, tippfehlr wrote:
> Did you already try to create a key with a fresh ~/.gnupg, eg. move
> ~/.gn
Did you already try to create a key with a fresh ~/.gnupg, eg. move
~/.gnupg to ~/.gnupg.bak and try again?
If that works, you can narrow it down to the config.
After entering the password, gpg generates the random bytes and prints
to use the system to gain entropy, so it’s likely that part that i
On Tue, 18 Jun 2024 04:58:04 -0500
"David C. Rankin" wrote:
> On 6/17/24 00:03, Carl Lei wrote:
> > What about: create a dedicated "git" user, and run apache as user
> > git? After all when new files are to be created they will have
> > owner=running program, which could be a CGI program launched
On 6/17/24 00:03, Carl Lei wrote:
What about: create a dedicated "git" user, and run apache as user git?
After all when new files are to be created they will have owner=running
program, which could be a CGI program launched from apache, or a git
program launched from SSH. If these are two differ
