Comment 6 for bug 26452

I just spent a few hours figuring out why I could not log in to my AFP
server and why Mac OS X gave me a "Could not connect to the server because
the name or password is not correct" message. I tracked it down to missing
DHX and missing SSL support. I was able to manually compile it using

You state that it is not possible to either
A) move netatalk to non-US; or
B) make a netatalk-ssl package; or
C) make a netatalk-dhx package
Due to licensing incompatibility between OpenSSL and Netatalk.

Could you explain, or point me to a legal source?

Obviously, I am allowed to compile it myself by first installing libssl-dev
and compiling netatalk from source.
So the culprit must be in the agreement how to distribute the binary code.

Reading the agreement from openssl at
http://www.openssl.org/source/license.html, it lists a.o.:
 * 2. Redistributions in binary form must reproduce the above copyright
 * notice, this list of conditions and the following disclaimer in
 * the documentation and/or other materials provided with the
 * distribution.

 * 6. Redistributions of any form whatsoever must retain the following
 * acknowledgment:
 * "This product includes software developed by the OpenSSL Project
 * for use in the OpenSSL Toolkit (http://www.openssl.org/)"

Given the current licence of netatalk, at
http://packages.debian.org/changelogs/pool/main/n/netatalk/netatalk_1.6.4-1/
copyright

What exactly limits you from adding the above (openSSL) copyright notice(s)
plus the licence file in the docs?

Kind regards,
Freek Dijkstra

PS: In the mean time, whoever reads this report, I am interested in a good
howto, for how to compile netatalk with DHX support myself, using apt-get (I
did it manually). That is a useful work-around as long as the distribution
licensing is not solved.