On Tue, Nov 23, 2021 at 1:40 PM Jason A. Donenfeld
<1892...@bugs.launchpad.net> wrote:
>
> I think he meant to post this on
> https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317
>
That makes a lot more sense. Commented my opinion there about the need
for key generation tooling.
I think he meant to post this on
https://bugs.launchpad.net/ubuntu/+source/wireguard/+bug/1950317
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892798
Title:
systemd package missing resolvconf(8)
@ahasenack I feel a bit lost here. This bug report is about how one
should or shouldn't propagate DNS servers after establishing a wireguard
based connection.
This has nothing to do w.r.t. creating keys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> Our kernel ships wireguard modules by default anyway, and one can
configure wireguard via networkd and soon via netplan. Which is our
default tooling to interact with the wireguard kernel module.
How should we generate the wireguard keys without `wg`? openssl? It's a
significant deviation from
** Tags added: resolved-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892798
Title:
systemd package missing resolvconf(8) compatibility symlink, and a
Provides: resolvconf
To manage
** Changed in: systemd (Debian)
Status: Unknown => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892798
Title:
systemd package missing resolvconf(8) compatibility symlink, and a
** Bug watch added: Debian Bug tracker #939904
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939904
Importance: Unknown
Status: Unknown
--
You received this bug notification
Your four appended comments are super full of just plain wrong
information. I'll try to unpack these all piecemeal:
> Ubuntu/Debian has never used openresolv
This is not the case. Ubuntu and Debian have provided openresolv for a
very long time, and resolvconf has mostly been an unmaintained
** Changed in: wireguard (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892798
Title:
systemd package missing resolvconf(8) compatibility symlink,
I'm not quite sure what is the point of wireguard package / wireguard-
tools on Ubuntu.
Our kernel ships wireguard modules by default anyway, and one can
configure wireguard via networkd and soon via netplan. Which is our
default tooling to interact with the wireguard kernel module.
wg /
Also see prior discussions on similar topic at
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713803
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892798
Title:
systemd package missing
Ubuntu/Debian has never used openresolv, and yes systemd-resolved had a
contribution to have openresolv compatible input interface.
I am not asking for wireguard to implement any legacy/compat interfaces,
but use directly systemd-resolved standard interface which has abi
guarantees.
There is a
Arch used to use openresolv, openresolv compat was added to systemd-
resolved, and yes hence they were able to switch to systemd-resolved
providing openresolv symlink / compat / integration. Either by default,
or as an option.
That is not possible for Debian/Ubuntu because of more than three
By the way, Arch manages the possibility of openresolv colliding with
systemd's resolvconf by providing a package called "systemd-resolvconf":
https://www.archlinux.org/packages/core/x86_64/systemd-resolvconf/
https://github.com/archlinux/svntogit-
14 matches
Mail list logo