lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070430172547.204810@gmx.net>
Date:	Mon, 30 Apr 2007 19:25:47 +0200
From:	"Uwe Bugla" <uwe.bugla@....de>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>,
	helge.hafting@...el.hist.no
Cc:	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-dvb@...uxtv.org
Subject: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and
 pseudo-authorities


-------- Original-Nachricht --------
Datum: Mon, 30 Apr 2007 17:56:17 +0100 (BST)
Von: Mauro Carvalho Chehab <mchehab@...radead.org>
An: Helge Hafting <helge.hafting@...el.hist.no>
CC: Uwe Bugla <uwe.bugla@....de>, linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org, akpm@...ux-foundation.org
Betreff: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and pseudo-authorities

> Hi Helge and others,
> 
> On Mon, 30 Apr 2007, Helge Hafting wrote:
> 
> >> what the consequence is. To be truthful I would strategically prefare a
> >> vacuum at the price that the work isn't even done for months.
> >> ONLY IF there is a personnel vacuum the necessity for others to
> volunteer 
> >> will arise.
> >> 
> > A sufficiently bad maintainer will also do it.  If lots of submitters
> send
> > their patches to andrew in order to get past a dysfunctional maintainer,
> > then the subsystem effectively is unmaintained.
> 
> The point is that Uwe patch will generate regressions by breaking for 
> Twinhan. His patch just removes compilation for dst and dst_ca on Kconfig,
> without taking care or driver internals. So, two initialization functions 
> won't be called by symbol_request(). Although those two functions will be 
> undefined, as the dvb will do the linkedition at module runtume (if 
> DVB_ATTACH is selected), modprobe won't detect the lack of those
> functions.
> At the end, cards with ST chips (DST and/or DST CA) will stop working, 
> without even printing a warning.

Mister Chehab, for the first and for the utmost last time now:

My deselection patch implies a very good text to strongly discourage the use of DST
and DST_CA in case someone does not know what he or she is doing. In so far the case that "cards with ST chips (DST and/ or DST CA) will stop working" will not happen at all.
This patch IS NOT DONE TO MAKE ANY DST OR DST_CA MODULE REQUIRING CARD WORK - 
THIS IS YOUR PART OF SO-CALLED LOGIC!!!!

THIS PATCH IS DONE TO AVOID RAM WASTE FOR CASES IN WHICH IT IS PROVEN THAT DST AND DST_CA ARE NOT NEEDED AT ALL!!!!

Example: Pinnacle PCTV SAT!!!

And once again and for the last time:

I did not manage to at least find one single unresolved module during compilation, and I have been working with this almost fantastic solution with several kernels for months now!

Above that I gave you every proof one can ever give: You received dmesg, you received configs, you received proven thesis, you received everything.

It would really be a perfect solution to bomb away the almost incredible meters thick wall in front of your head and your eyes.

And at this time I will stop responding to your mails - I got enough of you!!!
It's enough!!
> 
> I've tried to explain this to Uwe several times, but, at the end, he 
> always start insulting me and/or other developers.
> 
> Cheers,
> Mauro.

Happy reflection, Mister Chehab!!!!!

-- 
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ