Cybersecurity

5677 readers

115 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]

Notable mention to [email protected]

founded 1 year ago

MODERATORS

[email protected]

100

Millions of Docker repos found pushing malware, phishing sites (www.bleepingcomputer.com)

submitted 6 months ago by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 6 months ago (1 children)

I haven't used Synology, so I'm not sure. So I'll just explain a bit how Docker works, which will hopefully give some context.

Terminology:

image - the stuff hosted on https://hub.docker.com - basically the application and any dependencies it has
container - a disposable runtime for an image; stores new files separately from the image

By default, the container doesn't have access to anything that's not explicitly passed to it, kind of like a VM, but without the expensive overhead a VM has.

So the issues could be:

the image is incompatible with the host - pretty rare, but it happens
the container isn't started
the container doesn't have what it needs - maybe you need to expose a network port, or pass it a file
the Synology application isn't configured to use the container

For Synology and RustDesk specifically, I found this in the instructions:

Synology has two types of Docker, “Docker” and “Container Manager”. If you’re using DSM 7.2 and later, please follow the guide for DSM 7.2, or follow the DSM 6 guide if you’re on older system.

Synology DSM 7.2

Synology DSM 6

If you are using Synology with Portainer, please check this tutorial.

If I had a Synology system to test with, I'd look into it for you, but that's the best I've got. I run my own DIY NAS (old PC running openSUSE Leap w/ BTRFS, Samba, and minidlna configured).

[–] [email protected] 3 points 6 months ago

The other user on this thread pointed out, as you have, that they've updated the guide to include DSM 7s Container Manager, which is what I was originally trying it on to begin with. So, thanks to both of you, I now have a project to do this weekend to test out the updated guides! :)