diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009613.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-November/009613.html | 180 |
1 files changed, 180 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009613.html b/zarb-ml/mageia-dev/2011-November/009613.html new file mode 100644 index 000000000..7328eb631 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009613.html @@ -0,0 +1,180 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] (second attempt) suggesting sectool be dropped + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%28second%20attempt%29%20suggesting%20sectool%20be%20dropped&In-Reply-To=%3C4EC65FED.9010809%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009604.html"> + <LINK REL="Next" HREF="009596.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] (second attempt) suggesting sectool be dropped</H1> + <B>Claire Robinson</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%28second%20attempt%29%20suggesting%20sectool%20be%20dropped&In-Reply-To=%3C4EC65FED.9010809%40gmail.com%3E" + TITLE="[Mageia-dev] (second attempt) suggesting sectool be dropped">eeeemail at gmail.com + </A><BR> + <I>Fri Nov 18 14:38:53 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009604.html">[Mageia-dev] (second attempt) suggesting sectool be dropped +</A></li> + <LI>Next message: <A HREF="009596.html">[Mageia-dev] (second attempt) suggesting sectool be dropped +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9613">[ date ]</a> + <a href="thread.html#9613">[ thread ]</a> + <a href="subject.html#9613">[ subject ]</a> + <a href="author.html#9613">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 18/11/11 10:37, Colin Guthrie wrote: +><i> 'Twas brillig, and Claire Robinson at 17/11/11 12:49 did gyre and gimble: +</I>>><i> On 17/11/11 10:26, Michael scherer wrote: +</I>>>><i> On Tue, Nov 15, 2011 at 11:39:29AM +0100, Florian Hubold wrote: +</I>>>>><i> Am 15.11.2011 07:29, schrieb Michael Scherer: +</I>>>>>><i> Le lundi 14 novembre 2011 à 22:09 -0800, Robert M. Riches Jr. a écrit : +</I>>>>>>><i> (New list subscriber...needed to fix registered email address to +</I>>>>>>><i> post...) +</I>>>>>>><i> +</I>>>>>>><i> I was asked to submit this suggestion to the mailing list: +</I>>>>>>><i> +</I>>>>>>><i> As a Mageia user, I believe msec was much better off with_OUT_ +</I>>>>>>><i> sectool. In its present state, sectool is BADLY broken. It +</I>>>>>>><i> whines for pages about file permissions that are exactly as they +</I>>>>>>><i> should be. +</I>>>>>><i> Can you be more specific ? +</I>>>>><i> It think he means this: <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2808">https://bugs.mageia.org/show_bug.cgi?id=2808</A> +</I>>>>><i> or <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2255#c21">https://bugs.mageia.org/show_bug.cgi?id=2255#c21</A> or +</I>>>>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2255#c22">https://bugs.mageia.org/show_bug.cgi?id=2255#c22</A> +</I>>>>><i> +</I>>>>><i> I've also become supportive of this, sectool is basically duplicating +</I>>>>><i> partly msec functionality, there was no adaption for Mageia, +</I>>>>><i> currently it's +</I>>>>><i> checking on Mageia with the upstream Fedora configuration. +</I>>>>><i> +</I>>>>><i> Honestly this should have been done when importing it, as +</I>>>>><i> tmb already mentioned. msec should be patched to not require it. +</I>>>>><i> +</I>>>>><i> When we can't even get our default security tool to work properly, +</I>>>>><i> what's the point in adding a second one which needs even more +</I>>>>><i> maintenance? +</I>>>><i> +</I>>>><i> As you say, the question is again "why was it uploaded in the first +</I>>>><i> place". +</I>>>><i> It seems some packages were uploaded, and there seemed to have not enough +</I>>>><i> tests. While that's hard or impossible to avoid totally, that's not +</I>>>><i> really +</I>>>><i> the way to achieve a good distribution :/ +</I>>>><i> +</I>>>><i> I neither use msec or sectool, so I personnaly do not care that much. +</I>>>><i> Afaik, sectool was created by a ex mandriva/mandrake guy ( vincent +</I>>>><i> danen ), +</I>>>><i> because he was ( rightfully ) wanting to rewrite msec, who is/was +</I>>>><i> a mess of bash + python + perl code ( and rather ugly code, afaik, +</I>>>><i> last time +</I>>>><i> I took a look ), but if msec is supported, and sectool is not, then I +</I>>>><i> guess +</I>>>><i> we could drop. However, I still think we should first attempt to +</I>>>><i> collaborate +</I>>>><i> and fix it. ( ie, always have the reflex of "try to fix and +</I>>>><i> collaborate" ). +</I>>>><i> +</I>>><i> +</I>>><i> +</I>>><i> As one of the people who tested it and the one who filed the bug linked +</I>>><i> to above which expresses the need for it to be configured, I object to +</I>>><i> this being blamed on QA! It seems we are kicked whenever anything is wrong. +</I>>><i> +</I>>><i> I believe it is assigned to those higher up to provide a proper +</I>>><i> configuration. +</I>>><i> +</I>>><i> The bug was dated 22nd September and as yet no configuration exists. +</I>>><i> That does not reflect well on the distribution, not that QA haven't +</I>>><i> performed sufficient testing, which we obviously did. +</I>><i> +</I>><i> Knowing misc a little bit I don't think for a second he was intending to +</I>><i> blame QA team here. +</I>><i> +</I>><i> More the initial "blind import" (which was a hard time to do overly much +</I>><i> testing as I'm sure all will agree!) without properly checking things then. +</I>><i> +</I>><i> So please don't take it personally, I really don't think he was +</I>><i> targeting you :) +</I>><i> +</I>><i> Col +</I>><i> +</I>><i> +</I> +A bug was created for the issues found during testing to be resolved. No +new issues have arisen since then. + +What is being discussed now are only the issues raised by QA at the time +showing, if anything, that testing was quite thoroughly completed. No +extra testing time was necessary. + +I don't take this personally and I hope you will see this correction of +the facts in the same light. This is the second time in a week though +that QA has had to offer corrections against the assumption of a level +of neglect. + +Claire +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009604.html">[Mageia-dev] (second attempt) suggesting sectool be dropped +</A></li> + <LI>Next message: <A HREF="009596.html">[Mageia-dev] (second attempt) suggesting sectool be dropped +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9613">[ date ]</a> + <a href="thread.html#9613">[ thread ]</a> + <a href="subject.html#9613">[ subject ]</a> + <a href="author.html#9613">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |