-
Notifications
You must be signed in to change notification settings - Fork 20
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
Environment variable couldn't be all digital for SECURE_ID #169
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CERTTF-266.
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CERTTF-267.
|
It should already be string data though, right? It's the value for an env var. I'm curious why you are trying to assign binary data to it? |
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CERTTF-268.
|
I'm not. The |
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CERTTF-269.
|
This might be the limitation of
subprocess
, the error log as below while theSECURE_ID
is a valid HEX string123456
.The reason is
env_list.append(k + b'=' + os.fsencode(v))
will useos.fsencode
to encode the environment variables and check the data type should be string.It could change this line to
to solve this problem.
The text was updated successfully, but these errors were encountered: