[bug #54236] Leftover extra chars after C1 control's tty sanitization

Follow-up Comment #6, bug #54236 (project findutils): Thanks guys! Probably both patches are okay, but I cannot test them now, so I just trust you that they're indeed correct. Nit: I don't get why you call it a "workaround" in the commit message. Isn't this the correct fix?

[bug #54236] Leftover extra chars after C1 control's tty sanitization

Follow-up Comment #3, bug #54236 (project findutils): Sorry guys, I don't get what you're talking about, and I'm afraid you didn't understand my bugreport. Various quoting styles (as coreutils's "ls" has them) is only marginally relevant, and I can't see any security implication there, it's prima

[bug #54236] Leftover extra chars after C1 control's tty sanitization

URL: Summary: Leftover extra chars after C1 control's tty sanitization Project: findutils Submitted by: egmont Submitted on: Mon 02 Jul 2018 09:38:37 PM UTC Category: find

[bug #18576] -execdir vs. PATH

Follow-up Comment #4, bug #18576 (project findutils): "[...] then fail due to the security risk." - fail, really? Not just warn? ___ Reply to this item at: _

[bug #18554] feat req: -exec cmd {} more args +

Follow-up Comment #11, bug #18554 (project findutils): I can't see any _security_ problem with that construct, either. ___ Reply to this item at: ___ M

[bug #18554] feat req: -exec cmd {} more args +

Follow-up Comment #10, bug #18554 (project findutils): In addition to ARG_MAX (# bytes of args + environ for exec(), according to linux/limits.h) the Linux kernel has another limit: the number of command line arguments (including the 0th) cannot exceed 32767. Is this a standard, too? Is find/xarg

[bug #18554] feat req: -exec cmd {} more args +

Follow-up Comment #5, bug #18554 (project findutils): I'm just reading the standard you have linked, and I still can't see it explicitely stating that "{}" must _immediately_ precede the "+" sign. However, it says: "An argument containing only the two characters "{}" shall be replaced by the set

[bug #18554] feat req: -exec cmd {} more args +

Follow-up Comment #2, bug #18554 (project findutils): Yeah well... in the example, {} and + and next to each other. But I don't think we can count on the example, as it doesn't even mention that {} can be part of a longer argument, e.g. "exec utility_name [argument ...] foo{}bar +". So it is just

[bug #18554] feat req: -exec cmd {} more args +

URL: Summary: feat req: -exec cmd {} more args + Project: findutils Submitted by: egmont Submitted on: Tuesday 12/19/2006 at 12:58 Category: find Severity: 3 - Normal

[bug #14535] locate doesn't support UTF-8

URL: Summary: locate doesn't support UTF-8 Project: findutils Submitted by: egmont Submitted on: Wed 09/14/05 at 16:34 Category: locate Severit