Re: Restrict SSH to local network only except for Git users?
You might consider keeping your repo in an web/http directory for pulling and having your other users submit patches to you via eg email. That way you don't need ssh exposed to the public internet at all. That's how I have my self hosted git repos set up anyway. On Thu, Jul 27, 2023 at 09:24:56AM +0900, lain. wrote: > I have a pretty nifty network setup that allows me to host from home via > WireGuard. > But there's one thing I'm struggling with. > Because for security reasons, I made it impossible for people outside > the network to connect via SSH, but for Git to function properly, I need > to allow SSH only for git@(DOMAIN) or git@(PUBLIC IP), and redirect that > to my home network so they can do stuff like "git pull", "git push", and > all the other fancy stuff. > > My pf.conf rules look like this: > > pass in quick on wg0 proto tcp from 192.168.0.0/24 to any port 22 > > pass in on $externalinterface proto tcp from any to $externalip port 22 > > rdr-to $internalip > > block in quick on egress proto tcp from any to any port 22 > > And my sshd_config: > > AllowUsers lain@192.168.0.0/24 > > AllowUsers git@(DOMAIN) > > AllowUsers git@(PUBLIC IP) > > Where exactly am I doing wrong here?
Re: Restrict SSH to local network only except for Git users?
On Thu, Jul 27, 2023 at 10:28 AM lain. wrote: > > I have a pretty nifty network setup that allows me to host from home via > WireGuard. > But there's one thing I'm struggling with. > Because for security reasons, I made it impossible for people outside > the network to connect via SSH, but for Git to function properly, I need > to allow SSH only for git@(DOMAIN) or git@(PUBLIC IP), and redirect that > to my home network so they can do stuff like "git pull", "git push", and > all the other fancy stuff. > > My pf.conf rules look like this: > > pass in quick on wg0 proto tcp from 192.168.0.0/24 to any port 22 > > pass in on $externalinterface proto tcp from any to $externalip port 22 > > rdr-to $internalip > > block in quick on egress proto tcp from any to any port 22 > > And my sshd_config: > > AllowUsers lain@192.168.0.0/24 > > AllowUsers git@(DOMAIN) > > AllowUsers git@(PUBLIC IP) > > Where exactly am I doing wrong here? I suspect you're overthinking this. Rather than preventing access altogether, turn off password authentication and use SSH keys for authentication - for the git accounts, change the shell to git-shell if you haven't already. That way, bad faith actors can try all they want, they ain't gettin' in unless they get a hold of someone's key, and even if they do, it's likely a git key and the shell (barring any security vulns in git) will prevent them from doing anything not git related. -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
Restrict SSH to local network only except for Git users?
I have a pretty nifty network setup that allows me to host from home via WireGuard. But there's one thing I'm struggling with. Because for security reasons, I made it impossible for people outside the network to connect via SSH, but for Git to function properly, I need to allow SSH only for git@(DOMAIN) or git@(PUBLIC IP), and redirect that to my home network so they can do stuff like "git pull", "git push", and all the other fancy stuff. My pf.conf rules look like this: > pass in quick on wg0 proto tcp from 192.168.0.0/24 to any port 22 > pass in on $externalinterface proto tcp from any to $externalip port 22 > rdr-to $internalip > block in quick on egress proto tcp from any to any port 22 And my sshd_config: > AllowUsers lain@192.168.0.0/24 > AllowUsers git@(DOMAIN) > AllowUsers git@(PUBLIC IP) Where exactly am I doing wrong here?
Re: JH7110 - VF2
On 27/7/23 03:26, develo...@robert-palm.de wrote: Saw some commits for the JH7110. I flashed the latest RISCV snapshot miniroot73.img to an SD card and plugged it into the VF 2. Couldn't boot unfortunately. Commits on a master branch don't retrospectively magic their way into a previous release. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
JH7110 - VF2
Saw some commits for the JH7110. I flashed the latest RISCV snapshot miniroot73.img to an SD card and plugged it into the VF 2. Couldn't boot unfortunately. Is that already possible ? Or am I doing it wrong and there anything else to do than flashing the image ?
Re: RISCV mailing list
develo...@robert-palm.de wrote: > Zitat von Theo de Raadt : > > > develo...@robert-palm.de wrote: > > > >> I suggest a mailing list for the RISCV arch. > >> > >> Ok? > > > > > > It will be as popular and useful as the other per-architecture lists, > > meaning -- it is the wrong approach. > > Understand. Thanks. > > In consequence the other arch lists should be dropped as there is not > much traffic anyway? this is more like a who cares
Re: RISCV mailing list
Zitat von Theo de Raadt : develo...@robert-palm.de wrote: I suggest a mailing list for the RISCV arch. Ok? It will be as popular and useful as the other per-architecture lists, meaning -- it is the wrong approach. Understand. Thanks. In consequence the other arch lists should be dropped as there is not much traffic anyway?
Re: RISCV mailing list
develo...@robert-palm.de wrote: > I suggest a mailing list for the RISCV arch. > > Ok? It will be as popular and useful as the other per-architecture lists, meaning -- it is the wrong approach.
RISCV mailing list
I suggest a mailing list for the RISCV arch. Ok?
