Hi folks,
this package have been stuck while we were waitting for the OpenSSL
exception to be added to the Ossec's legal code. Today this exception
haven't been added, but Daniel Cid (upstream) wants to keep his code as GPL,
so we can continue working hoping to solve the OpenSSL issue later.
Jose,
Are you having discussions about this with the developer outside of their
mailing lists? From what I found on the different lists at
http://www.ossec.net/main/support/ there haven't been any updates since '09.
It seems to me that for them to add exception/s is a trivial change. Why
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi everyone,
about the last status update report:
- - secondary functionality was already included in last upstream code,
- - security concerns were overriden,
- - the license exception for OpenSSL haven't been included by upstream yet.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
Any news about the first 2 improvement ?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkyaRPMACgkQfwer1QPZVNIhjQCfXMxJofk98XZUhp38XlicltxL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all again,
an improvements list about ossec v2.3 was uploaded to upstream on April
13th, 2010.
This improvements are about license issues, how this software works
(security issues), and secondary functionality.
Now we are waiting for the first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
first of all, I'd like to thank Matej Vela for his last notes in this
thread, it was a very good place to start analyzing the package.
Today Ossec cannot be distributed by Debian because of a license issue
that was notified to the upstream
6 matches
Mail list logo
