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: <51EFAFD7.5070408@informatik.uni-leipzig.de>
Date:	Wed, 24 Jul 2013 12:43:35 +0200
From:	Florian Holz <holz@...ormatik.uni-leipzig.de>
To:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Guenter Roeck <linux@...ck-us.net>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [ 00/19] 3.10.1-stable review

Hi,

just a short comment.

I think, this snippet shows the key point in this argument:

At 15.07.2013 21:53 CEST +02:00 Sarah Sharp wrote:
> Good lord.  So anyone that is one of your "top maintainers" could be
> exposed to your verbal abuse just because they "should have known
> better"?
> 
> You know what the definition of an abuser is?  Someone that seeks out
> victims that they know will "just take it" and keep the abuse "between
> the two of them".  They pick victims that won't fight back or report the
> abuse.
> 
Sarah introduced the term "abuse" like in the first paragraph into the
discussion while complaining about the tone in some statements. It's her
claim, that all non-"polite" statements are an "abuse".

In the second paragraph, then she argues that "abuse" should be
prevented, using some definition of "abuse".

The claim that the unwanted kind of statements are really a kind of
abuse is still unfounded. She could have proven it -- eg by using
its/her/a definition -- but she only used this definition as foundation
to dislike the non-"polite" statements.

Imho this is just circular reasoning [1]
> (I) dislike -> (I regard as) impolite -> kind of abuse -> to be disliked (by all)
and so has no substance up to now. Maybe, logical package management
would have recognized this unmet dependency ;)

Disclaimer:
I dont' question the implication "abuse -> to be disliked".

Flo

[1] https://en.wikipedia.org/wiki/Circular_reasoning
--
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