Bug#825317: bash-completion: Un-escaped "~*" leads to spurious NSS lookups

2017-06-09 Thread TheSin
Since Debian is about to release, and this is an easy fix, shouldn’t we get this into testing ASAP? It’s really annoying how much larger this bug makes log files for a false positive. The fix has been listed for over a year, can it get added or is it still being tested?

Bug#825317: bash-completion: Un-escaped "~*" leads to spurious NSS lookups

2016-06-26 Thread Nathan Stratton Treadway
00-fix_quote_readline_by_ref.patch was introduced in bash-completion v1:2.1-3 as a fix for bug 739835 "filename completion broken with bash 4.3". https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739835 The patch file was originally pulled from Ubuntu, where it was created to fix two LP bugs:

Bug#825317: Bug #825317: bash-completion: Un-escaped "~*" leads to spurious NSS lookups

2016-06-26 Thread ge...@riseup.net
found 825317 1:2.1-4 thanks Hi Daniel, Thanks for reporting this. Actually, this issue is quite old; [1] points to the corresponding Ubuntu bug. According to this, just removing the patch fixes this issue, but I'm unsure about the potential downside(s) doing so and lacking time to check. All

Bug#825317: bash-completion: Un-escaped "~*" leads to spurious NSS lookups

2016-05-25 Thread Daniel Richard G.
Package: bash-completion Version: 1:2.1-4.3 Severity: minor Bug #825153 (mysterious "*" passwd queries in LDAP) turned out to be the result of a minor thinko in bash-completion. The _quote_readline_by_ref() shell function uses "~*" without the tilde being escaped (like all other instances of