Recent versions of leiningen (I've tested with 2.8.1) will refuse to download from http repositories.
The tutorial document suggests using
:repositories [["arachne-dev" "http://maven.arachne-framework.org/artifactory/arachne-dev"]]
, but leiningen will complain about this:
Tried to use insecure HTTP repository without TLS.
This is almost certainly a mistake; however in rare cases where it's
intentional please see `lein help faq` for details.
The relevant section of len help faq says:
Q: I got Tried to use insecure HTTP repository without TLS, what is that about?
A: This means your project was configured to download dependencies
from a repository that does not use TLS encryption. This is very
insecure and exposes you to trivially-executed man-in-the-middle attacks.
In the rare event that you don't care about the security of the machines
running your project, you can re-enable support for unprotected repositories
by putting this in your project.clj file:
;; never do this
(require 'cemerick.pomegranate.aether)
(cemerick.pomegranate.aether/register-wagon-factory!
"http" #(org.apache.maven.wagon.providers.http.HttpWagon.))
It's also possible you have a dependency which includes a reference to
an insecure repository for retrieving its own dependencies. If this
happens it is strongly recommended to add an :exclusion and report a
bug with the dependency which does this.
There is a workaround, but the best solution seems to be to add https support for the arachne repositories. Is that an option? Or is there other guidance you can provide to anyone looking to use arachne, but concerned about the security of downloading build artifacts over http?
(I'm not sure if this is the best of the various arachne repos to use to report this issue - if there's a better on, I can post it there.)
Recent versions of leiningen (I've tested with 2.8.1) will refuse to download from http repositories.
The tutorial document suggests using
, but leiningen will complain about this:
The relevant section of
len help faqsays:There is a workaround, but the best solution seems to be to add https support for the arachne repositories. Is that an option? Or is there other guidance you can provide to anyone looking to use arachne, but concerned about the security of downloading build artifacts over http?
(I'm not sure if this is the best of the various arachne repos to use to report this issue - if there's a better on, I can post it there.)