Bug#361954: new Alioth project, mail list, git repository && irc channel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi folks,
it's a pleasure to announce that thanks to Javier Fernández-Sanguino we
have recently created an Alioth project called *pkg-ossec* [1] to track
the Ossec's packaging process.
There we have a git repository and a mail list for development purposes
[2] where you can track and discuss the recent and forthcoming commits.
We have created an irc channel at irc.debian.org called #pkg-ossec.
And please, take a look at [3] if you want more information about how to
contribute to this project as it contains most of the policy we'll use
to handle the code.
Thanks for all your contributions.
See you there,
[1] https://alioth.debian.org/projects/pkg-ossec/
[2] https://lists.alioth.debian.org/mailman/listinfo/pkg-ossec-devel
[3] http://www.eyrie.org/~eagle/notes/debian/git.html
On 22/03/11 23:38, Jose Antonio Quevedo wrote:
> 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.
> There are two ways to avoid the OpenSSL exception: disabling OpenSSL or
> migrate the code from OpenSSL to GNU/TLS.
>
> Now we already know, thanks to Javier Fernandez-Sanguino, that we can
> disable OpenSSL and make it work pretty easily.
>
> But the other question would be, what do you think about the impact of
> disabling openssl on Ossec? OpenSSL has some interesting features that
> should be considered.
> We can disable OpenSSL and make it work, but doing this we could be
> releasing a dangerous software, so IMHO it would be quite interesting to
> have an OpenSSL-2-GNUTLS.patch.
>
> Now I'm looking for the way to publish the source code of this package
> as it's developed.
> Maybe you already know a good place to do this and would like to share?
> Then please, let us know. I'm thinking in a git repository.
>
> Happy hacking,
>
> 2011/3/1 Ciarán Handley <ciaran@linux.ie <mailto:ciaran@linux.ie>>
>
> 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 this taking so long? What can we do to
> speed this up a bit? I took the liberty of making the 'suggestion'
> on their request page
> (http://ossec.uservoice.com/forums/18254-general/suggestions/1543503-debian-package),
> if people would like to vote it up.
>
> Cheers,
> Ciarán
>
>
>
>
> --
> Jose Antonio Quevedo Muñoz
> Key fingerprint: C88A AAFA CF91 F556 E1D5 52FC C3D7 3C5D 8224 5822
> --
> Ever tried. Ever failed. No matter.
> Try again. Fail again. Fail better.
> ~ Samuel Beckett ~
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAEBCAAGBQJOJMzKAAoJEMPXPF2CJFgiI9oQAJJyWzNj1zG0VefubSK0adyR
rWaPRVazeTy/AQW/hjp907VC+RPM5ZazHmsb7cdH8qznv/rLvoG3/fCJKuciv23o
2y5bbLQ00mR0tkcnluKVhTCJ3e+x83nhLPvIQx1CrBl7bmULBivFGUbUlv0UKj9U
TZ8wJhAcoYZacwXh73j/aQZxmT2KsuzozitZtP3CA0TsdcFHDJ8m3cpFkeo22/ZQ
leinFapG+pbMmdl2QU597qVUfG7+kToDKyuYzhBF9+vfBDFJQR7Q9VPCgoY8ZwpA
L2JiSqPpwUEC6RYLzBw0AXLEnwavb8BOW1v/xUTkClUb5bE09ai/SDWizYq7EEN0
3FpPrET4raIU84y2bk6cALLKkNfl7quONNj8oTpflXAcVfYDgGnhtNjMPjzS/SYv
c48K0x2ijjMWesxy8tVXGxmnqd5+gN8pruDYBh4VPcD5s2OBmBnI6iuyVxfIiSig
PUpFk/LcDSxHpgkww+b4vE/LVzVu2tBe0n7e5yMcUSXpU76UVNumaJ3e0KAzOH3c
wh/DsA//NdFJXuxfyE9XR98bPmiCnZutawdHu3Sc8wo1GchgkgcWOejMwX6/kBfo
mw2SL+08lD8TkS1w0bLov3/BRmYlxWByjWtI6aofwSoWzDAhHb18a2/l/1CVcNFm
2OFryHKzBqz35B8QdZnn
=mzs7
-----END PGP SIGNATURE-----
Reply to: