en Copyright 2025 Java http://opengrok.net:8080/history/src/sys/contrib/libsodium/README.markdown#3611ec604864a7d4dcc9a3ea898c80eb35eef8a0 Merge ^/head r337646 through r338014. List of files: /src/sys/contrib/libsodium/README.markdown Sat, 18 Aug 2018 12:15:54 +0000 Dimitry Andric <dim@FreeBSD.org> http://opengrok.net:8080/history/src/sys/contrib/libsodium/README.markdown#3611ec604864a7d4dcc9a3ea898c80eb35eef8a0 Merge ^/head r337646 through r338014. List of files: /src/sys/contrib/libsodium/README.markdown Sat, 18 Aug 2018 12:15:54 +0000 Dimitry Andric <dim@FreeBSD.org> http://opengrok.net:8080/history/src/sys/contrib/libsodium/README.markdown#0ac341f145426f1f0d00b64d35f19fada2be635c Bring in libsodium to sys/contribBring in https://github.com/jedisct1/libsodium at461ac93b260b91db8ad957f5a576860e3e9c88a1 (August 7, 2018), unmodified.libsodium is derived from Daniel J. Bernstein et al.'s 2011 NaCl("Networking and Cryptography Library," pronounced "salt") software library.At the risk of oversimplifying, libsodium primarily exists to make it easierto use NaCl. NaCl and libsodium provide high quality implementations of anumber of useful cryptographic concepts (as well as the underlyingprimitics) seeing some adoption in newer network protocols.I considered but dismissed cleaning up the directory hierarchy anddiscarding artifacts of other build systems in favor of remaining close toupstream (and easing future updates).Nothing is integrated into the build system yet, so in that sense, nofunctional change. List of files: /src/sys/contrib/libsodium/README.markdown Fri, 17 Aug 2018 00:23:50 +0000 Conrad Meyer <cem@FreeBSD.org> http://opengrok.net:8080/history/src/sys/contrib/libsodium/README.markdown#0ac341f145426f1f0d00b64d35f19fada2be635c Bring in libsodium to sys/contribBring in https://github.com/jedisct1/libsodium at461ac93b260b91db8ad957f5a576860e3e9c88a1 (August 7, 2018), unmodified.libsodium is derived from Daniel J. Bernstein et al.'s 2011 NaCl("Networking and Cryptography Library," pronounced "salt") software library.At the risk of oversimplifying, libsodium primarily exists to make it easierto use NaCl. NaCl and libsodium provide high quality implementations of anumber of useful cryptographic concepts (as well as the underlyingprimitics) seeing some adoption in newer network protocols.I considered but dismissed cleaning up the directory hierarchy anddiscarding artifacts of other build systems in favor of remaining close toupstream (and easing future updates).Nothing is integrated into the build system yet, so in that sense, nofunctional change. List of files: /src/sys/contrib/libsodium/README.markdown Fri, 17 Aug 2018 00:23:50 +0000 Conrad Meyer <cem@FreeBSD.org> http://opengrok.net:8080/history/src/sys/contrib/libsodium/README.markdown#3611ec604864a7d4dcc9a3ea898c80eb35eef8a0 Merge ^/head r337646 through r338014. List of files: /src/sys/contrib/libsodium/README.markdown Sat, 18 Aug 2018 12:15:54 +0000 Dimitry Andric <dim@FreeBSD.org> http://opengrok.net:8080/history/src/sys/contrib/libsodium/README.markdown#0ac341f145426f1f0d00b64d35f19fada2be635c Bring in libsodium to sys/contribBring in https://github.com/jedisct1/libsodium at461ac93b260b91db8ad957f5a576860e3e9c88a1 (August 7, 2018), unmodified.libsodium is derived from Daniel J. Bernstein et al.'s 2011 NaCl("Networking and Cryptography Library," pronounced "salt") software library.At the risk of oversimplifying, libsodium primarily exists to make it easierto use NaCl. NaCl and libsodium provide high quality implementations of anumber of useful cryptographic concepts (as well as the underlyingprimitics) seeing some adoption in newer network protocols.I considered but dismissed cleaning up the directory hierarchy anddiscarding artifacts of other build systems in favor of remaining close toupstream (and easing future updates).Nothing is integrated into the build system yet, so in that sense, nofunctional change. List of files: /src/sys/contrib/libsodium/README.markdown Fri, 17 Aug 2018 00:23:50 +0000 Conrad Meyer <cem@FreeBSD.org>