SslHttpClient.java:50-52: Using the provided...

[0pdd]

The puzzle 67-80672d59 from #67 has to be resolved:

docker-java-api/src/main/java/com/amihaiemil/docker/SslHttpClient.java

Lines 50 to 52 in 873268e

	* @todo #67:30min Using the provided certificates,
	* register the http/https protocols, similar to how "unix" is
	* registered in UnixHttpClient.

The puzzle was created by amihaiemil on 08-May-18.

Estimate: 30 minutes,

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

[0crat]

@amihaiemil/z please, pay attention to this issue

[0crat]

@0pdd/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot!

[0crat]

Job #100 is now in scope, role is DEV

[0crat]

The job #100 assigned to @llorllale/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this

[amihaiemil]

@llorllale This is a rather complex task. The big outline is that we need to first read the contents of the certificates, then use them to create objects of type KeyStore and such (from the JDK), which will go to some Factory from Apache -- that's how the guys from Spotify did it here but if you have a better idea, feel free to say it. This, of course, can be a research task as well :D

[llorllale]

@amihaiemil this here...

    /**
     * Ctor.
     * @param certs Path to the folder containing the following certificates:
     *  ca.pem, cert.pem and key.pem.
     */
    SslHttpClient(final Path certs, final char[] passwd) {

Is cert.pem the docker server's public key?

Some references:

• https://stackoverflow.com/a/18542079/1623885
• https://stackoverflow.com/a/32513368/1623885

[llorllale]

@0crat waiting

[0crat]

@0crat waiting (here)

@llorllale The impediment for #100 was registered successfully by @llorllale/z

[amihaiemil]

@llorllale

Is cert.pem the docker server's public key?

Yes, I think so, param Path certs points to a folder containing the following certificates: ca.pem, cert.pem and key.pem. key is the private key and I assume cert is the public one. These 3 are created when you create a remote docker host using dockermachine.

I assume you spent the time researching (or more, let me know if so). So just edit the puzzle with the resources that you found :D

[llorllale]

@amihaiemil is this supposed to be two-way or one-way tls?

[amihaiemil]

@llorllale two-way, that's my understanding, since we don't have other authentication mechanism between the docker client and the remote docker host.

[llorllale]

@amihaiemil and is ca.pem the server's public key? I'm confused because "ca" sounds like "certificate authority", which would definitely not be docker.

[amihaiemil]

@llorllale yes, I think it is the server's public key as well.

ca.pem - server public key -- the server's public key issues by the CA, right? I think that's why the name is ca.pem
cert.pem - client certificate
key.pem - client key

[llorllale]

@0crat waiting for review/merge on #120

[0crat]

@0crat waiting for review/merge on #120 (here)

@llorllale Job #100 is already on hold

[amihaiemil]

@0crat boost 6x

[0crat]

@0crat boost 6x (here)

@amihaiemil Boost 6x was set for #100

[0crat]

Boosting tasks is against our principles, see §15: -10 point(s) just awarded to @amihaiemil/z

[0crat]

Order was finished: +90 point(s) just awarded to @llorllale/z

[0crat]

The job #100 is now out of scope