[Touch-packages] [Bug 1719062] Re: systemd-resolved malformed packet on cert dns lookup

I have upgraded to version 234-2ubuntu10. It doesn't make a difference. I double checked and requested the key (cert record) using dig and it works just fine, no malformed packet. It's only when gpg2 requests it combined with systemd-resolved where there is a problem as far as I can tell. -- Yo

[Touch-packages] [Bug 1719062] Re: systemd-resolved malformed packet on cert dns lookup

To clarify, having dig request it from systemd-resolved works. Having dig request it directly from the server also works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1719

[Touch-packages] [Bug 1719062] [NEW] systemd-resolved malformed packet on cert dns lookup

Public bug reported: systemd-resolved returns a malformed packet when looking up an openpgp key (via a cert record rfc4398) from my internal authoritative dns server. The command I used was gpg2 -v --auto-key-locate=clear,cert,local --locate-keys [Email Address] This works correctly if I change

[Touch-packages] [Bug 1687482] Re: -4 flag doesn't work

I've figured out that it is caused by this line in /etc/ssh/ssh_config ProxyCommand /usr/bin/sss_ssh_knownhostsproxy -p %p %h This was put there by the freeipa installer (ipa-client-install), so I guess this is a freeipa or sssd bug. -- You received this bug notification because you are a membe

[Touch-packages] [Bug 1687482] Re: -4 flag doesn't work

Although it could still be a bug in ssh if ssh doesn't do ProxyCommand correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1687482 Title: -4 flag doesn't work Statu

[Touch-packages] [Bug 1687482] Re: -4 flag doesn't work

I'm running xenial. After I saw your comment I tried it on zesty and have yet to run into this bug on zesty. I haven't tried in the same environment yet though, I can try that later this week as well as get an apport-collect done. As you can see below, the last login reports an ipv6 address. I

[Touch-packages] [Bug 1687482] [NEW] -4 flag doesn't work

Public bug reported: Whenever I use the -4 flag on ssh, it still uses the ipv6 address from dns instead of forcing ipv4 like it says it is supposed to do in the man page. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because y