I am running a simple service to tweak SSHD on first boot (the script is at the
bottom of this mail). This is on Debian Bookworm incase it makes any difference.
If I configure my service as:
[Unit]
Description=ITS Generate SSH Server Keys
Wants=ssh.service
Before=ssh.service
[Service]
ExecStart=
On Sunday, 14 April 2024 at 15:21, Andrei Borzenkov wrote:
> If whatever your script does involves (re-)starting of sshd service, you
> have deadlock with "oneshot" - sshd service cannot proceed until your
> service startup completes and your service apparently waits on something
> that waits
Could someone point me into the right systemd service file hardening parameters
to give a DynamicUser access to a Linux socket operated by another process ?
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
On Sunday, 22 December 2024 at 22:13, Kevin P. Fleming
wrote:
> systemd-resolved does not write or otherwise modify /etc/resolv.conf;
So you're saying this statement at the top of /etc/resolv.conf is a lie ?
$ cat /etc/resolv.
On Sunday, 22 December 2024 at 22:13, Kevin P. Fleming systemd-resolved does not write or otherwise modify /etc/resolv.conf; your
> system may have a symlink at /etc/resolv.conf which points to one of the
> files created by systemd-resolved. Whatever tool or method is managing that
> is the o
At present systemd-resolved inserts 127.0.0.53 into /etc/resolv.conf
Certain applications on my system have problems with this, relating to DNSSEC
and they work perfectly with the "proxy-only" 127.0.0.54 instead.
What is the permanent way to ensure that systemd-resolved inserts .54 and not
.53
On Monday, 23 December 2024 at 07:45, Daniel Foster wrote:
> I believe you can just remove the symlink at /etc/resolv.conf and
> replace it with a file that points to 127.0.0.54.
>
Thanks Daniel, that has been my work-around, a systemd timer checking for
127.0.0.53 and doing a sed on /etc/re
On Monday, 23 December 2024 at 13:10, Itxaka Serrano Garcia
wrote:
> Hallo there!
>
> If using systemd-resolved, cant you just configure the DNS in
> /etc/systemd/resolved.conf or /etc/systemd/resolved.conf.d/ directly so it
> setups your desired address?
My DNS servers are currently manu
Sent with Proton Mail secure email.
On Monday, 23 December 2024 at 14:00, Kevin P. Fleming
wrote:
> The simplest fix is to set "DNSSEC=no"
That seems to me to be a bit of a "sledgehammer to crack a nut".
The man page for resolved.conf says:
"It is recommended to set DNSSEC= to true on
Sent with Proton Mail secure email.
On Monday, 23 December 2024 at 12:23, Adam Nielsen
wrote:
> But what's the underlying issue? Maybe there's a different fix?
Its been a while so I can't remember the exact details, but I know its to do
with Postfix.
Postfix creates a copy (not symlin
10 matches
Mail list logo
