Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: enviroment variables $HOSTNAME usable in GPOs #1037

Open
2 tasks done
simonwolfBHS opened this issue Jun 22, 2024 · 1 comment
Open
2 tasks done

Feature: enviroment variables $HOSTNAME usable in GPOs #1037

simonwolfBHS opened this issue Jun 22, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@simonwolfBHS
Copy link

Is there an existing request for this feature?

  • I have searched the existing issues and found none that matched mine

Describe the feature

Our company is aiming to restrict the sudoer privilege very strict and for each computer individually.
Therefore for windows we have stared to create goups for this purpose e.g. secLoaclAdmin-DEVMACHINE01
In the Windows policies we are able to substitute the Hostname with a env variable %COMPUTERNAME% and thus in turn applies the correct group to the machines.

Unfortunately the adsys policy Ubuntu > Client management > Privilege Authorization > Client administrators is not honoring $HOSTNAME and only writes this as text into the file /etc/polkit-1/localauthority.conf.d/99-adsys-privilege-enforcement.conf

Describe the ideal solution

Ideally this adsys policy would start to accept $HOSTNAME as a variable and processes this accordingly on the machine

Alternatives and current workarounds

we are creating a seperate GPO per machine which is leading to very cluttered GPO mgmt

Ubuntu users: System information

No response

Non Ubuntu users: System information

adsys version: adsysctl 0.14.1build1 adsysd 0.14.1build1
Distribution: Ubuntu 24.04 LTS (Nobel Numbat)

Additional information

No response

Double check your logs

  • I have redacted any sensitive information from the logs
@didrocks
Copy link
Member

That’s a sensible and interesting feature. Thanks for suggesting this!

I don’t think we have the time to work on it this immediately, but it can be a good first contribution for anyone interested if someone wants to beat us before we have a chance tackling this.

Tagging as such.

@didrocks didrocks added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants