Skip to content

Commit

Permalink
Turns out the no-TLS workaround does actually work.
Browse files Browse the repository at this point in the history
  • Loading branch information
technomancy committed Jan 19, 2018
1 parent c5bf1b5 commit 26bca98
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion doc/FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -232,7 +232,16 @@ property.
**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.
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 or can ensure that the only http
traffic is going out over a trusted network, you can re-enable support
for unsafe 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
Expand Down

0 comments on commit 26bca98

Please sign in to comment.