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

Consider preserving LANG and LC_ environments #30

Open
Earnestly opened this issue May 19, 2020 · 2 comments
Open

Consider preserving LANG and LC_ environments #30

Earnestly opened this issue May 19, 2020 · 2 comments

Comments

@Earnestly
Copy link

As far as I understand it, these environments are perhaps not as necessary under OpenBSD due to their UTF-8 only approach. But I find it necessary to often preserve them as there isn't a C.UTF-8 available yet from either glibc or musl.

Would it make sense for OpenDoas to preserve these environments?

@ericonr
Copy link

ericonr commented Apr 12, 2021

Oh, I was going to open an issue for this!

setenv { LANG=$LANG } in a config is enough for what I suppose are most of the "default" setups, but it's very possible that people use different values for each of the LC_* variables. The question is, does this warrant being exported by default, or should it be sysadmin policy?

Are there known state "corruptions" using LANG and/or LC_* env vars that could be considered security concerns?

@Tachi107
Copy link

As far as I know sudo also preserves (only) the LANG env var, and that's enough in most cases. If a user has a non-default set of LC_* variables than it probably means that it should also manually adapt doas.conf to its custom setup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants