https://bugzilla.redhat.com/show_bug.cgi?id=1198498
--- Comment #22 from Andy Green <a...@warmcat.com> --- I pushed a patch on v1.6-stable (and master) https://github.com/warmcat/libwebsockets/commit/ebfdb0d24d9555d745d2457d0691a4ae9770624b It lists in LICENSE the disposition of sources that had other licences. I also took the opportunity to make the test apps public domain (cc-zero) since they are intended to be adapted by users into their own code without any 'viralness'. +3) Some sources included have their own, more liberal licenses, or options +to get original sources with the liberal terms. + +Original liberal license retained + + - lib/sha-1.c - 3-clause BSD license retained, link to original + - win32port/zlib - ZLIB license (see zlib.h) + +Relicensed to libwebsocket license + + - lib/base64-decode.c - relicensed to LGPL2.1+SLE, link to original + - lib/daemonize.c - relicensed from Public Domain to LGPL2.1+SLE, + link to original Public Domain version + +Public Domain (CC-zero) to simplify reuse + + - test-server/*.c + - test-server/*.h That's tagged as v1.6.3 About the ciphers, yes unless lws has some reason to do something fixed itself, things can be set at runtime by the user code with a reasonable default if not. As you say the library doesn't enforce anything about ciphers itself but the code using it may do so if it wants. Otherwise it just uses what the SSL library defaults to. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review
