19994e3286
run prettier
2023-02-21 17:54:39 +02:00
4a20f75d3c
etc/systemd/resolved.conf.d: add DNS0 DoT configs
...
Their website already had the correct syntax for the entries
Ref: #153
2023-02-20 11:49:31 +02:00
36c2688cec
etc/systemd/system/unbound.service.d/never-fail.conf: unbound isn't allowed to fail either
2023-02-03 10:59:31 +02:00
bb7f283891
Revert "systemd/matterbridge.service: import parts of upstream"
...
This reverts commit 35aea33043
.
Ref: https://github.com/42wim/matterbridge/issues/1794
2022-04-04 09:50:46 +03:00
35aea33043
systemd/matterbridge.service: import parts of upstream
...
https://github.com/42wim/matterbridge/wiki/Service-files#systemd
2022-04-04 08:35:23 +03:00
82ef806e9f
systemd-resolved README: add quickstart, remove extra h-levels
2022-03-28 20:43:03 +03:00
17da76e484
systemd/resolved/README.md: add the ArchWiki DNSSEC issue links
2022-03-28 20:37:37 +03:00
f55c00dae6
systemd/resolved/README.md: add missing word, improve formatting
2022-03-28 20:36:11 +03:00
8c532e3ef8
etc…resolved…: add/clarify links in/to comments
...
Courtesy of https://wiki.archlinux.org/title/Systemd-resolved#DNSSEC
2022-03-28 20:34:37 +03:00
d47c374706
etc/ststemd/resolved…: aggressive cleanup/rewriting
2022-03-28 20:28:17 +03:00
64bba542b1
systemd/matterbridge.service: remove -debug, mention /groupId
2022-03-18 10:44:25 +02:00
76814f830f
etc/{i2pd,systemd}: modernise to less bad ideas
...
The issue has been fixed last year and considering I2Pd can connect
through Yggdrasil natively, tunneling Yggdrasil in is a bad idea and
could lead into Yggdrasil over Yggdrasil loop situation.
2022-03-08 18:18:40 +02:00
1356fccd20
systemd: add flatpak-update.{service,timer}
...
Resolves : #121
2021-12-18 13:45:53 +02:00
1b4ac2b6d7
etc/systemd/system.conf.d: add log4shell.conf
2021-12-13 13:09:35 +02:00
5704353d55
systemd: copy matterbridge restarter into gitea one
...
It used to stop working randomly without a good reason, but that is
likely fixed upstream a long time ago and while I removed it from cron,
these units exist so should the issue recur, I can throw these back in.
The cron wasn't randomized though, but I don't think there is harm in
this being a bit random.
2021-12-06 23:48:40 +02:00
8e69874534
matterbridge-restart.timer: fix language
2021-12-06 23:48:30 +02:00
bd91ef704d
systemd: matterbridge.timer -> matterbridge-restart.{service,timer}
...
Resolves : #98
2021-11-22 09:56:56 +02:00
9ba056cfd3
matterbridge-cleanup.service: fix typo, ignore exit state
2021-11-21 17:15:12 +02:00
62573195d9
systemd: add matterbridge-cleanup.{service,timer}
...
Resolves : #98
2021-11-21 17:11:44 +02:00
13278214d1
matterbridge.timer: OnBootSec=0 just in case
...
Ref: #98
2021-11-21 16:59:05 +02:00
29f7cf6b98
systemd: first attempt at matterbridge restarter timer
...
Ref: #98
2021-11-21 16:52:14 +02:00
4f50f4a367
systemd-resolved: don't DNSSEC with adblocking
2021-11-21 11:37:03 +02:00
12fe7a59a8
etc/systemd/resolved: add configuration for Mullvad DoT
2021-11-21 11:16:11 +02:00
12127744b5
systemd: also keep trying Chrony
2021-10-03 09:58:59 +03:00
84e714b55e
systemd: keep retrying yggdrasil, don't sleep
2021-10-03 09:58:03 +03:00
a5836327c4
etc: pipewire & bluetooth: enable codes, battery reporting
...
https://web.archive.org/web/20210614103423/https://www.redpill-linpro.com/techblog/2021/05/31/better-bluetooth-headset-audio-with-msbc.html
2021-06-14 13:36:34 +03:00
126918d98d
systemd/limnoria.service: add TZ env & RestartSec
2021-06-02 17:50:30 +03:00
c1768cae67
systemd: "rewrite" supybot -> limnoria, move znc, rmdir irc/
2021-05-16 18:00:31 +03:00
306270c441
etc/systemd: rm cjdns & miredo, I am unlikely to use them again
2021-05-16 11:15:34 +03:00
c8e89a5817
systemd: add coredump.conf.d/biggercores.conf
2021-02-18 14:47:23 +02:00
a0c61231f4
systemd/resolved.conf.d: add snopyta-strict.conf
...
While posting an example how I would do it I might as well put it here
2021-02-10 16:12:42 +02:00
b20f3367b1
systemd/yggdrasil: add mullvad-exclude (& fix chrony override typo)
2020-12-09 09:38:49 +02:00
40d535f2c0
systemd/chrony.service.d/mullvad-exclude: actually fix this
2020-12-08 18:36:34 +02:00
0c7038da14
systemd: systemd-resolved.service.d/unbound.conf: After unbound
2020-10-30 10:19:39 +02:00
fe83cbbb3a
systemd: add config for excluding Chrony from Mullvad
2020-10-30 08:04:58 +02:00
993759577e
Bind systemd-resolved to Unbound
2020-10-25 09:05:07 +02:00
1e70d7d4d7
etc/systemd-resolved&unbound: add Quad9 ECS configs
...
Untested. The last time I saw the documentation, they didn't mention
DoT.
2020-10-21 17:09:20 +03:00
31a15a9abc
systemd-resolved & unbound: update AdGuard IPs
...
Resolves : #81
2020-09-27 14:34:54 +03:00
cf8dc85ec0
systemd/timesyncd.conf.d: add cloudflare.conf
2020-08-09 10:51:36 +03:00
82cf5e7742
systemd/resolved.conf.d: add generic NextDNS confs
2020-08-09 00:07:06 +03:00
73fb88e11d
systemd-resolved.conf.d: everywhere -> 00-everywhere
2020-07-24 12:16:31 +03:00
69f55cd724
systemd/resolved: adguard-strict -> adguard-dot
2020-07-18 14:05:36 +03:00
550b68d149
etc/systemd/resolved: add [adguard,cloudflare}-strict.conf
...
I am not actually using either though and I am not sure if I will,
but maybe they are nice to have as a backup here just in case.
2020-07-18 02:20:56 +03:00
b3cb953b9c
systemd/resolved: add a comment to everywhere.conf too
...
as every other file explains who it is for, why not this
2020-07-04 19:09:26 +03:00
0ae22081a0
etc/systemd-resolved: rework all files more or less
...
* explain things in README.md, don't duplicate comments
* opportunistic-insecure.conf should be used everywhere by default, so
thus it's now everywhere.conf. However I am yet to test it does what
I expect, so this is bad case of testing in production or after
committing it in general.
2020-07-04 19:06:18 +03:00
7a73088beb
systemd/resolved.conf.d/quad9*.conf: enable SNI
2020-06-26 12:22:09 +03:00
bce9af0edd
resolved.conf: add quad9-compat.conf
2020-06-26 12:22:09 +03:00
d1fc83913b
systemd/user: add ipfs, transmission-daemon (from system)
2020-03-30 08:42:06 +03:00
b217baaec9
systemd/system: update syncplay-server.service
...
It never got the TLS flag apparently
2020-03-27 18:02:34 +02:00
64d5fef6f3
ipfs.service: point to the new meta issue
2020-02-29 18:03:32 +02:00