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: <1415225591.3444747.187568145.134CEE91@webmail.messagingengine.com>
Date:	Wed, 05 Nov 2014 23:13:11 +0100
From:	Martin Tournoij <martin@...242.net>
To:	"Theodore Ts'o" <tytso@....edu>,
	Austin S Hemmelgarn <ahferroin7@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC] The SIGINFO signal from BSD

On Wed, Nov 5, 2014, at 20:31, Austin S Hemmelgarn wrote:
> The people to talk to about that for the core 
> utilities on Linux would be the maintainers of the GNU coreutils, or 
> whatever your distribution might use in their place (I think it's very 
> unlikely that busybox or toybox would implement it however).

Well, if the kernel doesn't provide the feature, then we can be sure it
will never be implemented :-)
I thought this was a good place to start asking,, and even if GNU
coreutils opt to not implement this for whatever reasons, other
applications still can (mine will!)
Besides, there are already many tools which use this feature when
available, these would for with no or minimal adjustments.


On Wed, Nov 5, 2014, at 21:14, Theodore Ts'o wrote: 
> In a world where we have a GUI desktop, I suspect implementing ^T is
> much less interesting but if someone were to submit a patch to at
> least make ^T send a SIGINFO, I can't think of a reason why it
> wouldn't be accepted.  (BTW, if you're going to do this, note that ^T
> could be remapped to any control character via stty; so to do this we
> would need to define an extra index in c_cc[] array in the struct
> termios.)

Thanks, this is what I needed :-) I wondered if there is a specific reason
it's not implemented, or if it was just something no one ever did.

I can start my investigation in the kernel sources ;)

Thanks,
Martin
--
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