Hi Marc,

> Ok, and what's about potential security holes? Should they be discussed
> publicly?

No. You could email the private@ mailing list of the project - or just
mail me directly if you want for WSS4J or CXF issues.

Colm.

On Tue, Aug 30, 2011 at 6:02 PM, Marc Giger <[email protected]> wrote:
> Hi Colm,
>
> On Thu, 25 Aug 2011 17:33:41 +0100
> Colm O hEigeartaigh <[email protected]> wrote:
>
>> Hi Marc,
>>
>> Do you mean for this project or for all Apache WS-related projects? If
>> the former, then this list is fine. I don't think there is any
>> cross-project mailing list relating to security. In any case, I think
>> CXF/Rampart/etc folk with an interest in security keep an eye on this
>> list.
>
> Ok, and what's about potential security holes? Should they be discussed
> publicly?
>
> Thanks again!
>
> Kind regards
>
> Marc
>
>
>>
>> Colm.
>>
>> On Thu, Aug 25, 2011 at 4:47 PM, Marc Giger <[email protected]> wrote:
>> > Dear devs,
>> >
>> > Where to discuss security relevant topics in apache ws-projects?
>> >
>> > Kind regards
>> >
>> > Marc
>> >
>> >
>> > --
>> > Lesson 1: Cryptographic protocols should not be developed by a
>> > committee. -- Niels Ferguson and Bruce Schneier --
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>> >
>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> http://coheigea.blogspot.com/
>> Talend - http://www.talend.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
> --
> Lesson 1: Cryptographic protocols should not be developed by a
> committee. -- Niels Ferguson and Bruce Schneier --
>



-- 
Colm O hEigeartaigh

http://coheigea.blogspot.com/
Talend - http://www.talend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to