DNS exploit of Systemd

Chat about Linux in general
Forum rules
Do not post support questions here. Before you post read the forum rules. Topics in this forum are automatically closed 6 months after creation.
User avatar
xenopeek
Level 25
Level 25
Posts: 29611
Joined: Wed Jul 06, 2011 3:58 am

Re: DNS exploit of Systemd

Post by xenopeek »

Lot of creative commands here :) Let's use systemctl status systemd-resolved to check status of the service instead.

On Linux Mint 18.x is shows it is installed but disabled and inactive:

Code: Select all

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:systemd-resolved.service(8)
On LMDE 2 you'll get a response that shows you're not using systemd.

Code: Select all

Failed to get D-Bus connection: Unknown error -1
Even if you had enabled it on Linux Mint 18.x or installed systemd on LMDE 2 and enabled it, I think like Spearmint2 said you're fine in your own home as you're using your ISP's DNS. Whether you're using systemd-resolved or not, when you take you devices out of your home to some public network that's is where the risks are. You should be using a VPN when you connect your devices to public networks.
Image
Faust

Re: DNS exploit of Systemd

Post by Faust »

I've been following this issue with interest , and I tried members tips to find out if systemd is active on my system

On Mint 17.3 64-bit Cinnamon this command -
systemctl status systemd-resolved

gives " command not found " , even running as root .

Anybody know why that might be ?
User avatar
xenopeek
Level 25
Level 25
Posts: 29611
Joined: Wed Jul 06, 2011 3:58 am

Re: DNS exploit of Systemd

Post by xenopeek »

Faust wrote:On Mint 17.3 64-bit Cinnamon this command -
systemctl status systemd-resolved

gives " command not found " , even running as root .
Linux Mint 17.x did not use systemd yet.
Last edited by xenopeek on Sun Jul 02, 2017 7:32 am, edited 1 time in total.
Reason: Apparently how I answered this earlier was reason to restart a flameware over systemd. I've moved all those (including my) comments to archive.
Image
Locked

Return to “Chat about Linux”