Bug#361954: [ossec-dev] OpenSSL exception
So what exactly needs to be added to the license? I will send that to
the Trend team for addition...
Also, OpenSSL doesn't need to be added (and everything should work
fine). In fact, that's how we support
systems without openssl-dev installed... We just link to it for small
performance gains (when generating the
sha1 hashes).
thanks,
2011/8/1 Jose Antonio Quevedo Muñoz <joseantonio.quevedo@gmail.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi everyone,
>
> I'm packaging your software, Ossec, for Debian [1] and, there's an
> ambiguity issue between GPL and OpenSSL licenses when they are being
> redistributed together.
>
> It would be great if you could add the OpenSSL exception to Ossec's
> legal code as it's described in this email [2] because, although I
> already have a patch to avoid linking against OpenSSL, and sysadmins can
> use other software (like OpenVPN) to send information through OpenSSL
> tunnels, this is an interesting feature that I'm sure we all would be
> glad of being able to use in our Ossec server-agent installation.
>
> I'll be waitting for your answer here or within your code.
>
> Thanks in advance,
>
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361954
> [2] http://lists.debian.org/debian-legal/2004/05/msg00595.html
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQIcBAEBCAAGBQJONzmnAAoJEMPXPF2CJFgiCTQP/jFLpAshgTv+u4/MnKO8p7VP
> tLD/huEFDy9aGx49cIATNsWkgWNEmWltVVMxae8dNgeU0L9Gbql7XeQSkYY2d6Ny
> mJYJbIa+OmhRRS1iQq6H8XoUvWPviafbG7Ljjoc322sJqfcRgbJC7XomUuiFbrYD
> FRjUpT86HUrm5SPFhHsRQsaFhGzPQO2dbxR4DP+rsQoKCZe//J92tSlDeubjJnjg
> 4lE6VZDhgTPInAM9aWKLX4nvE6sN0UhVI2/styd30t3Gg7/YMRrezUWZduaMcAoR
> vDFbP4iKBllGQDkDcihTbhw5yM/9FFm0F8PKFENXsa3re3DPGSTv8m//wXxPhjCH
> J+rUaWg2QTQFBo2UQ2NrZ74OMraqUYfEyViVQUbJXQIp07bePWWcCRZSVvXZlofE
> OSXY0+NUkx5Ksafn2cp+cgLBNo3e+SeDtBdZMs5kT+ObO3fkYhFfNU8ooc47M/Pk
> S+oVJ1dVHRCj+gGpY5211w60sIAPjQhUym5VlUwiToSbynNiWRrBWjkJ9QnsuVlJ
> cy4vFSZ2KrX0ZcSO4yIQXhgnq9buTujLSffFVAp0R5Q5qszCuC53aH7+VREppwbA
> p4tNgkkC50YAiLYIMStgNSJRBoa5QLWTCoqKLo0GYa2PsCbDoHIPGw4/Jd6icfqy
> 0v4mwvfgdVHJXNGoluuN
> =Cj4n
> -----END PGP SIGNATURE-----
>
Reply to: