Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
On 2/19/08, Jan-Oliver Wagner [EMAIL PROTECTED] wrote: Hi, I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html Naturally, I am in favour of all 4 of them :-) I'm in favour of all 4 too. Sergio, ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
Hi, On Wednesday 20 February 2008 01:08, Jan-Oliver Wagner wrote: I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html I'm in favor of all four change requests. Bernhard pgp26NSOr46EY.pgp Description: PGP signature ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
On Mittwoch, 20. Februar 2008, Thomas Reinke wrote: #2 Insufficient knowledge of use scenarios to form a vote opinion, but comments as follows: NSR is, AFAIK, not broken w.r.t semi-colons. The actual NTP protocol has the same issue of being line oriented - the server replaces all semi-colons with newlines. NSR just carries this issue through to its code. Thus removing NSR does not solve the semi-colon issue, that can only be done by adding support to both client and server to support escaped semi-colons. As such, using the semi-colon problem as a justification to remove NSR doesn't make sense. Indeed it is only a first step to remove the design flaw. Fixing the protocol bug should be one of the next CRs (which will have much more impact on compatibility. I've extended the CR accordingly. Best Jan -- Dr. Jan-Oliver WagnerIntevation GmbH, Osnabrück Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/ Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
#1 Adding script_oid(): In favour. #2 Insufficient knowledge of use scenarios to form a vote opinion, but comments as follows: NSR is, AFAIK, not broken w.r.t semi-colons. The actual NTP protocol has the same issue of being line oriented - the server replaces all semi-colons with newlines. NSR just carries this issue through to its code. Thus removing NSR does not solve the semi-colon issue, that can only be done by adding support to both client and server to support escaped semi-colons. As such, using the semi-colon problem as a justification to remove NSR doesn't make sense. #3 Removal of plugin factory: In favour. #4 Plugin upload: In sufficient knowledge of use scenarios to form a vote opinion. Thomas Jan-Oliver Wagner wrote: Hi, I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html Naturally, I am in favour of all 4 of them :-) However, please read and judge whether it is a good or bad idea or wether it needs further refinement. I am not totally sure about the proper voting scheme. Tim, Robert: Does SPI require something special or do we just decide upon a simple voting? Best Jan ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
[Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
Hi, I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html Naturally, I am in favour of all 4 of them :-) However, please read and judge whether it is a good or bad idea or wether it needs further refinement. I am not totally sure about the proper voting scheme. Tim, Robert: Does SPI require something special or do we just decide upon a simple voting? Best Jan ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
On Wednesday 20 February 2008 00:08:24 Jan-Oliver Wagner wrote: Hi, I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html Naturally, I am in favour of all 4 of them :-) However, please read and judge whether it is a good or bad idea or wether it needs further refinement. I am not totally sure about the proper voting scheme. Tim, Robert: Does SPI require something special or do we just decide upon a simple voting? The full details as we expressed them in the constitution can be found at http://seedsforchange.org.uk/free/consens, but it essentially comes down to a show of negative hands. If noone raises strong objections against an idea then we can proceed. One thing that isn't defined is the period in which people need to respond in order for an objection to be considered. In the past I've seen people work on the 24 hour rule, but since we're spread across multiple continents and time zones, I'd propose a longer period. OTOH we can't have an indefinite period of time. How about 48 hours with an gentlemens agreement not to start a call for voting over weekends. Tim -- Tim Brown mailto:[EMAIL PROTECTED] http://www.nth-dimension.org.uk/ ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Re: [Openvas-discuss] [Openvas-devel] Voting on Change Requests #1 - #4
On Feb 19, 2008 7:35 PM, Tim Brown [EMAIL PROTECTED] wrote: On Wednesday 20 February 2008 00:08:24 Jan-Oliver Wagner wrote: Hi, I'd like to call for voting on the change requests #1 - #4, listed here: http://www.openvas.org/openvas-crs.html Naturally, I am in favour of all 4 of them :-) However, please read and judge whether it is a good or bad idea or wether it needs further refinement. I am not totally sure about the proper voting scheme. Tim, Robert: Does SPI require something special or do we just decide upon a simple voting? The full details as we expressed them in the constitution can be found at http://seedsforchange.org.uk/free/consens, but it essentially comes down to a show of negative hands. If noone raises strong objections against an idea then we can proceed. One thing that isn't defined is the period in which people need to respond in order for an objection to be considered. In the past I've seen people work on the 24 hour rule, but since we're spread across multiple continents and time zones, I'd propose a longer period. OTOH we can't have an indefinite period of time. How about 48 hours with an gentlemens agreement not to start a call for voting over weekends. 48 Hours sounds good to me. We should be able to make exceptions to the rule if someone has given advanced notice of not being available for a certain time period as well. -RB -- Robert Berkowitz 919.244.5704 [EMAIL PROTECTED] ___ Openvas-devel mailing list [EMAIL PROTECTED] http://lists.wald.intevation.org/mailman/listinfo/openvas-devel ___ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
