#Problem with ssl injection and self-signed certificate

1 messages · Page 1 of 1 (latest)

pliant slate
#

Hello,
I am forced to use an ssl inspection/injection tool on my workstation. Each https request will be arived with a self signed certificate.
By using the dagger tool I always receive the following error:

x509: certificate signed by unknown authority

I found in the archiv the following instruction. Is this still valid and will it work?
https://archive.docs.dagger.io/0.2/1224/self-signed-certificates/

I tried it out an receive the same error as before.
Can I completly disable the ssl verification?
Do you have any other tip? Thanks

The connection to a container registry or to a remote docker daemon might require the need to add self-signed CA certificate signed by unknown authority.

elfin nimbus
#

Hey there, this is a known limitation of Dagger Modules, we are working on a fix, work is being tracked here: https://github.com/dagger/dagger/issues/6599

Unfortunately, there is no great workaround right now for Dagger Modules.

With that being said, things should still work for non-module code (anything that uses dagger run) We are moving a lot of docs around right now, but following a guide from the 0.9x branch should get you a bit further

https://archive.docs.dagger.io/0.9/

GitHub

What is the issue? For security reasons many companies man-in-the-middle all SSL traffic to the internet with their own certificate. This causes a x509: certificate signed by unknown authority issu...

cedar crest
#

With that being said, things should still work for non-module code (anything that uses dagger run) We are moving a lot of docs around right now, but following a guide from the 0.9x branch should get you a bit further
@elfin nimbus is there a specific guide from this that would help here?