As it is stated in Arch Wiki, wine is safe free to use. Now it says some things like running Wine under separate accounts which I understand but there are some others that I don't. Can someone share some tricks so we can reduce or completely illuminate the risk?

What is the risk you are concerned about?

Well... Virus mostly. If there is anything else that I should be concerned at all. Now I suppose I don't have to create another account, I can just not run Wine using "sudo" or "doas" and I'll be fine. But the Arch Wiki talks about other stuff that I don't understand so I wonder if there are other things the I should be aware of.

Understood but Windows viruses cannot affect Linux. It certainly couldn’t hurt to run wine as another user though. Maybe create another account and use that for wine only so you have separation from your normal user?

1 members found this post helpful.

Ok! That's one thing! I will do that for sure! In the meanwhile, I will wait for any other suggestions. Thanks a lot!

Any time you install software there is a risk.

Many programs that are common have what might be called "users" that do the work. Those users need permissions. If you are worried then don't use it.

Wine is just a non-privileged userland program that implements a useful subset of the WinXX API so that many Windows programs are able to run. There are no particular "risks" associated with using it.

It's always a good idea, though, to do all of your daily work from one or more "ordinary" users who are not "administrators" – they are not members of the wheel group and therefore cannot say: "sudo su". Each user has a particular purpose – accounting, maybe servicing a particular client – and each one's home directory isn't accessible to anyone else. None of them can "manage the system." None of them can walk into a telephone booth and fly out wearing funny blue tights. So, if any rogue software tried to do anything nasty, it would find itself incapable of doing so.

In my experience, computers are really bad at knowing when to say "yes," but they're really good at saying "no."

2 members found this post helpful.

OK, I'm not 100% sure about this, but how about installing "playonlinux"?
This can create a "bottle" for every wine program, which separates their environment. All for one user.
Has anyone tested if this is safe (in the sense rempas asked)? Or has a good source?
I use playonlinux myself for other reasons (easy removing wine programs one of them) and like it.

Playon versus wine, dunno. I kind of trust wine more but I get your point of bottle.

The OP hasn't really expressed what part of this is suspect. Is it the windows program or wine.

you can try this dockerized wine too: https://hub.docker.com/r/scottyhardy/docker-wine/ if you wish.

It's not so much playonlinux versus wine. playonlinux runs on top of wine (and not without) and gives some extra features...

True...

Don't give wine more access to your file system than it needs. Keep the win drives in their own containers. For instance, don't map X: to your home directory.