Closed bweben closed 1 year ago
Thank you for your feedback. This has been routed to the support team for assistance.
route to CXP team
Hello @bweben We are routing this to Service Teams Attention for further action!
I am having exactly the same issue as well
I am also getting this libssl related error when I try any az command on Ubuntu 22.04. It can't run any az command at all.
Iast 're-routing' of this issue was over 2 weeks ago... any updates on whether this is being tracked / analyzed? @SatishBoddu-MSFT? @yonzhan
Same Problem for me
---> Interop+Crypto+OpenSslCryptographicException: error:0E076071:configuration file routines:module_run:unknown module name
Is there any possibility to get this working even without a new az version? This is quite a high priority issue for us. Or are there any other Microsoft support options available for the Azure CLI? I am sorry if this is the wrong channel to ask but if anyone has any answer to my questions I would be happy to hear them.
Same Problem for my ubuntu 22.04
No usable version of libssl was found
./config.sh:行 86: 1414825 已放弃 (核心已转储) ./bin/Agent.Listener configure "$@"
Come on - I know this is an open source project of Microsoft / Azure.. but no activity whatsoever in over a month? Are you serious?
The workaround for now is the following:
wget http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb && sudo dpkg -i libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb && rm libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb
sed -i 's/openssl_conf = openssl_init/#openssl_conf = openssl_init/g' /etc/ssl/openssl.cnf
See https://github.com/microsoft/azure-pipelines-agent/issues/3834#issuecomment-1173182107
Hi @kysucix Thanks for the workaround... this is maybe a temporary solution, but libssl1 / openssl1 have serious CVEs! (https://security-tracker.debian.org/tracker/CVE-2022-1292 for example) I really hope libssl3 is soon going to work!
Hi, the vulnerability is fixed in latest version of libssl, see https://ubuntu.com/security/CVE-2022-1292
@yonzhan Do you have an update for a proper fix to this issue?
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @v-anvashist, @V-hmusukula.
Author: | bweben |
---|---|
Assignees: | - |
Labels: | `Service Attention`, `customer-reported`, `Artifacts`, `DevOps`, `Auto-Assign` |
Milestone: | Backlog |
Hi, the vulnerability is fixed in latest version of libssl, see https://ubuntu.com/security/CVE-2022-1292
Yes, we found a patched version that we can use. Still we think that installing libssl1 on an os that comes with libssl3 is an ugly hack. Unfortunately it seems to be the only way right now to get az artifacts working on ubuntu 22.04.
The workaround for now is the following:
- Install an older version of libssl:
wget http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb && sudo dpkg -i libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb && rm libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb
- Edit etc/ssl/openssl.cnf:
sed -i 's/openssl_conf = openssl_init/#openssl_conf = openssl_init/g' /etc/ssl/openssl.cnf
same same, az artifacts universal download
also fails on ubuntu 22.04. workaround above works...
Issue reproduced on Win11/WSL2/Ubuntu 22.04 Workaround with installing http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1l-1ubuntu1.6_amd64.deb and commenting line in /etc/ssl/openssl.cnf openssl_conf = openssl_init Works fine
The link to the mentioned package did not work for me. I could however use http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1-1ubuntu2.1~18.04.20_amd64.deb to get it working. (Remember to edit the package name three (3) times in the command (wget, dpkg and rm))
This issue also seems to exist when running an azure pipeline agent locally
same here, i use ubuntu 22.04 and want to install azure pipeline agent, but get this error
+1. Oddly I have the agent Azure Dev Ops agent working on some of my Ubuntu 22.04 VMs but not others. Is there a fix for this yet?
Any news on this topic? I don't think that downgrading the lib is a good option for me
I have the same issue, any updates?
If you’re issue is with the ADO pipeline, they have updated the main bug being tracked here: https://github.com/microsoft/azure-pipelines-agent/issues/3834#issuecomment-1325638361
Good news, they have an update that will move to dotnet 6, so the issue will be resolved soon!
From an Ubuntu 22.04
docker container, I am getting the SSL error while running az artifacts universal download
.
This was opened back in April. How is it still not fixed? I feel like the workaround is unacceptable, because people will end up installing a package that will never ever get updated and will probably forget to readjust their openssl config.
What is the timeline for a real fix?
@SatishBoddu-MSFT @yonzhan Is any update on this?
Looks like updating az cli .NET core to latest 2.1 version should work: https://dev.to/n3wt0n/no-usable-version-of-the-libssl-was-found-solved-2ffa
@SatishBoddu-MSFT @yonzhan Is any update on this?
Looks like updating az cli .NET core to latest 2.1 version should work: https://dev.to/n3wt0n/no-usable-version-of-the-libssl-was-found-solved-2ffa
The post you linked talks about missing 1.0. In our case, it's complaining about missing 1.1, not 1.0. We need it to support 3.0.
Yes, we need support for OpenSSL 3.0.
I agree, it's a pain to maintain the workaround suggested above.
any updates??
Is there a timeline when /if the feature is planned?
This is very annoying, Thinking of a possible workaround using a docker container so as to not cripple your workstation
Put this into your .bashrc. It works in some, but not all cases, you will have to try...
function az () {
docker run -it -u $UID:$GID --entrypoint="" -v "$(pwd)":/build --workdir="/build" -v "${HOME}"/.azure:/.azure:rw -v "${HOME}"/.azure-devops:/.azure-devops:rw mcr.microsoft.com/azure-cli az "$@"
}
export -f az
PS 14.04.2023: The docker image is broken, too. It is already for a few weeks. Don't bother with this solution
Nice, I didn't know MS published the tool as a container. Thanks
This is also broken on the latest container 2.46.0.
You must understand that this is a major issue and it is not fixed after almost a year. We are considering moving to an alternative artifact platform capable of storing the build and universal artifacts so that developers and testers may download them without hitting this problem.
I'd like to ask you MS Devs to please fix it, with as much urgency as possible.
Any chance this will get fixed? Looks a bit weird that such a mainstream distro is not supported, even more than one year after its release.
@yonzhan / @SatishBoddu-MSFT this ticket got moved around a few times but has never actually been worked on, right? can you please reconsider it?
@lorenzo-biava @yonzhan @SatishBoddu-MSFT
Also the related issue on the extension itself is rather stale: https://github.com/Azure/azure-cli-extensions/issues/5979
HI dear Microsoft, can you please fix this issue?
The libssl version changed the new working commands are:
wget http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2_amd64.deb && sudo dpkg -i libssl1.1_1.1.1f-1ubuntu2_amd64.deb && rm libssl1.1_1.1.1f-1ubuntu2_amd64.deb
sudo sed -i 's/openssl_conf = openssl_init/#openssl_conf = openssl_init/g' /etc/ssl/openssl.cnf
Hey guys,
Did a quick investigation, and this is issues within the ArtifactTool.exe .NET application that is downloaded while running az artifacts universal download
or az artifacts universal publish
. Tldr this app uses EOL version of .NET (Core 3.1), which is no longer supported. Additionally,
Unfortunately as this is Microsoft closed-source tool, instead of relying on Github team to fix it here, this needs to be raised on Developer Community. There is a slight chance that updating that tool to latest supported LTS version of .NET may resolve this issue - there is ticket open for it already. I think the best approach would be to make some noise there, so perhaps someone from development team of that tool would spend some effort to make it working with current Linux stack.
I already noticed that Microsoft has a pretty nasty tendency there to close tickets related to this tool with "not enough information" or "workaround provided. install libssl 1.x", so keep in mind that we really need to escalate it properly.
Thanks @Azkel ! Great investigation! Thank you also for the last advice ;)
May 2023, I am glad I found this thread but also sad that this issue is still present. Is there any work being done to fix this problem?
May 2023, commenting for exposure.
Experiencing the same issue, would love a better solution than using an outdated vulnerable ssl library.
HI dear Microsoft, can you please fix this issue?
The libssl version changed the new working commands are:
wget http://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl1.1_1.1.1f-1ubuntu2_amd64.deb && sudo dpkg -i libssl1.1_1.1.1f-1ubuntu2_amd64.deb && rm libssl1.1_1.1.1f-1ubuntu2_amd64.deb
sed -i 's/openssl_conf = openssl_init/#openssl_conf = openssl_init/g' /etc/ssl/openssl.cnf
This fix worked for me.
Please fix this m$....
Another workaround:
function az () {
docker run -it -u $UID:$GID --entrypoint="" -v "$(pwd)":/build --workdir="/build" -v "${HOME}"/.azure:/.azure:rw -v "${HOME}"/.azure-devops:/.azure-devops:rw mcr.microsoft.com/azure-cli az "$@"
}
@jaapcrezee Are you sure this work with this image? For me it seems to have the same issue.
@rodrigovb96 I use version 2.45.0 Maybe you can try that one instead of the latest.
It looks like latest azure-cli doesn't need the workaround anymore.
Can someone else confirm as well?
I can also confirm that the latest version v2.50.0 of Azure CLI doesn't need any workaround (at least I tested on Ubuntu Jammy).
Description
We upgraded our docker image to ubuntu 22.04 from 20.04. Now
az artifacts universal publish
fails due to aNo usable version of libssl was found
error. If we install the libssl version1.1.*
we end up with another error.On the Ubuntu 20.04 docker image, all worked great.
Versions
Logs
Error with libssl 1.1.*
Error with libssl 3.0.*
Az extension versions
Azure cli version
OS version
Update: Manual reproduction