You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The additional package 'ca-certificates' in line 3 is necessary to verify the certificate.
And this is the point which -in my opinion- breaks the two-stage-approach, if the url of the repository is changed to https:
In line 19 of Dockerfile/etc/apt/sources from stage 1 is copied to stage 2.
In line 22 the package informations are updated via apt-get update.
This will fail, because there is no certificate information for https://download.webmin.com in this stage. But without this step it is not possible to add ca-certificatesto this stage (which is needed for running apt-get update without error, which is needed to install ca-certificates…).
I think using https only for retrieving the key should be o.k.:
The key is retrieved over a secured connection
The packages are retrieved over an unprotected connection, but they are checked with the key.
If you look into the /etc/apt/source.list on your system, the urls for the repositories from Debian or Ubuntu are all "only" http.
If the url for the repository should also be switched to https then the concept have to be switched to one stage and the following changes have to be made:
This is more a question, but these lines below appear unsafe to me, are they?
Adding a key and repository without https opens up the possibility of installing packages from a MITM attack.
The text was updated successfully, but these errors were encountered: