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.

Sign up for GitHub

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

Jump to bottom

'sudo config' output is always localized #108

Open
brunvonlope opened this issue Oct 10, 2024 · 1 comment
Open

'sudo config' output is always localized #108

brunvonlope opened this issue Oct 10, 2024 · 1 comment
Labels
Issue-Task It's a feature request, but it doesn't really need a major design. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@brunvonlope
Copy link

Sudo for Windows version

1.0.1

Windows build number

10.0.26100.0

Other Software

I am trying to make a .ps1 script that relies on sudo for Windows and I need to ensure that the host machine config mode is set to 'normal' mode.

But running 'sudo config' outputs a localized message:

PS C:\Users\bruno> sudo config
O Sudo está atualmente no modo Embutido neste computador

I consider this a bug because this way the tool is simply non-portable.

Steps to reproduce

  1. Run sudo config

Expected Behavior

English message

Actual Behavior

Portuguese (Brazil) message
@brunvonlope brunvonlope added Issue-Bug Something isn't working Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 10, 2024
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
5afdfce 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center online certification.

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka built-in) mode...
3. in a Windows account in admin group

The second and, specially, the last one are harsh but this is the design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
fc6ea9c 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center online certification.

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka built-in) mode...
3. in a Windows account in admin group

The second and, specially, the last one are harsh but this is the design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
58d0ff1 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center online certification.

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka built-in) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
6d9452f 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center's online certification.

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka built-in) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
bd2b0ec 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center's online certification.
(Just to note: On Windows SDK, certification is not equal to signing.
It's more a checklist process to see if the package is suitable to run.)

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka built-in) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
c9b8697 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center's online certification.
(Just to note: On Windows SDK, certification is not equal to signing.
It's more a checklist process to see if the package is suitable to run.)

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka built-in) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
299f983 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center's online certification.
(Just to note: On Windows SDK, certification is not equal to signing.
It's more a checklist process to see if the package is suitable to run.)

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka inline) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
76f740a 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center's online certification.
(Just to note: On Windows SDK, certification is not equal to signing.
It's more a checklist process to see if the package is suitable to run.)

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka inline) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
61562bc 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center's online certification.
(Just to note: On Windows SDK, certification is not equal to signing.
It's more a checklist process to see if the package is suitable to run.)

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka inline) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Oct 13, 2024
@brunvonlope
build/windows: Add (optional) WACK phase to MSIX script
9a6b93c 
Local certification with WACK is optional and useful to anticipate if
the MSIX will be refused by Partner Center's online certification.
(Just to note: On Windows SDK, certification is not equal to signing.
It's more a checklist process to see if the package is suitable to run.)

To avoid needing the full script to be run with admin rights (which
would be scary) this feature only works with a bunch of requirements:
1. sudo for Windows (so Windows 11 24H2)...
2. enabled in normal (aka inline) mode...
3. in a Windows account in admin group

The 2nd and, specially, the last one are harsh but this is sudo's design:
microsoft/sudo#108
microsoft/sudo#68
@zadjii-msft zadjii-msft added Issue-Task It's a feature request, but it doesn't really need a major design. and removed Issue-Bug Something isn't working labels Dec 6, 2024
@zadjii-msft
Copy link
Member

Hmm. Good catch about this - we should definitely include a non-localized version of this from the CLI.

in the meantime, you should be able to workaround this by looking at the values in

reg query HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Sudo
reg query HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\Sudo

The Policies one will act as a max for the value in CurrentVersion, if it's set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Task It's a feature request, but it doesn't really need a major design. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @brunvonlope