3

I’m trying to run a professional health software on WINE, but it fails at some point with the following error message (� = non-rendered accentuated character):

Permissions pour 'Everyone': 1301ff
Aucun droit de contr�le total trouv� pour 'Everyone'.
Contr�le total accord� � Everyone pour le fichier C:\windows/galss.ini

Translation:

Permissions for 'Everyone': 1301ff
No full control right found for 'Everyone'
Full control granted to Everyone on file C:\windows/galss.ini

How can I grant full access to Everyone (bad practice, I know, but I’m not the software’s dev) to that file using WINE?

I’ve tried the WINE file explorer, but it does not give me the option to change the permissions.

Or am I totally off-base, and user permissions is not a thing within WINE?

EDIT: For anyone wondering, this is what I’m trying to reproduce: https://doc.ubuntu-fr.org/soins2000, but that documentation seems very out-of-date.

Improve this question
4
  • 1
    See askubuntu.com/questions/892176/… . Also, have you tried using wine to run the app's installer, or have you unpacked the app and used wine app.exe to run it? Sometimes one works better than the other. Note that some apps make Windows-specific calls and just won't run in wine. C'est la vie. Commented 23 hours ago
  • @DrMoishePippik I have used WINE to install the app Commented 6 hours ago
  • 2
    Ini files in system root is an artifact of a previous Windows architectural model. It does not necessarily imply that the file permissions are wrong or are the resolution. The application requires the ability to modify the ini file. The message is somewhat misleading in that regard. Commented 3 hours ago
  • 1
    @GregAskew Yes, it’s totally possible that the error message is misleading. Also, the software itself smells of legacy code, so remnants of old, discouraged practices don’t surprise me. Commented 3 hours ago

2 Answers 2

Reset to default
4

How can I grant full access to Everyone (bad practice, I know, but I’m not the software’s dev) to that file using WINE?

File ACLs reported by Wine are a hardcoded translation of the Unix file modes. There does not seem to be any option for fine-grained control.

In the hardcoded translation, "Full control" is not reported because this would imply "Take ownership", which Wine has no way to perform in its current "everything just runs as the user" architecture (a user cannot 'chown' files on Linux and there is no equivalent file-level permission granting that access).

You can patch mode_to_sd() in server/file.c if really necessary.

Alternatively you might look for some way to make Wine report the filesystem as FAT rather than NTFS (as FAT doesn't have file security), but I don't know if that's doable without patching the code either, or if your program won't complain about that as well.

Or am I totally off-base, and user permissions is not a thing within WINE?

NTFS-style file permissions kind of "exist" in Wine, as they are an integral part of the API that Wine emulates, but they exist only as a bare-minimum, hardcoded-value implementation, without any of the underlying "business logic".

Wine doesn't do its own security enforcement (i.e. does not emulate this part of Windows) – apps running under Wine have exactly the same access as native Linux programs (and each user's Wine environment is its own separate "world" that doesn't interact with another user's Wine), and until now it hasn't had the need to implement anything more flexible than that.

Improve this answer
1
  • Damn, that’s what I feared. I’ll have to find a way to get some vendor’s support, but they provide very little Linux support, and even their Windows software development skills seem suboptimal. Commented 6 hours ago
2

The best way to run that software might be in a virtual machine (VM).

  • The environment of the VM is fully controllable.
  • It's quite easy to install a VM such as VirtualBox on Linux, though for Windows 11 in particular, you'll need to set flags such as BypassTPMCheck.
  • If the software needs to connect to the outside world, you'll need to configure the VM accordingly.

My small experience with a VM is that it is surprisingly fast, both to boot and to run applications, and that the software behaves as if it were running on the actual OS rather than a VM.

Improve this answer
2
  • I appreciate your suggestion of using a VM, but that would defeat the goal of getting rid of Windows. Plus, I know that at least one person managed to make it work in the past and this is what I’m trying to replicate. I might eventually have to do it, but that’ll be my last-ditch solution. Commented 6 hours ago
  • 1
    @breversa, agreed -- I've no desire to use Windows any longer, but have kept it as a secondary OS for apps that are simply not wine-compatible. See the wine Application Database for compatibility with well-known apps, but you likely will not find that particular professional health software listed. Commented 3 hours ago

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.