Gunnar Hjalmarsson wrote:
Adam Jimerson wrote:
According to perlsec I need to use it as a key in a hash or reference a
substring. The example given is
,[ ]
if ($data =~ /^([...@\w.]+)$/) {
$data = $1; # $data now untainted
} else {
die Bad data in '$data'; # log this
matt wrote:
This is usually the result of a mismatch between the character set
used by your ssh client and the locale settings of your session.
Here's a link that discusses:
http://help.lockergnome.com/linux/high-ascii-characters-linux-terminal-
ssh-ftopict487060.html
[u...@host ~]$ echo
Adam Jimerson wrote:
I attached my code for my program,
You don't say what to do if the untainting fails. This code:
if ($name =~ /^([...@\w.]+)$/) {
$name = $1;
};
should better be:
if ($name =~ /^([...@\w.]+)$/) {
$name = $1;
On Fri, Jan 9, 2009 at 6:30 PM, Adam Jimerson vend...@charter.net wrote:
Gunnar Hjalmarsson wrote:
Adam Jimerson wrote:
According to perlsec I need to use it as a key in a hash or reference a
substring. The example given is
,[ ]
if ($data =~ /^([...@\w.]+)$/) {
$data =
Hi there. Since the charset doesn't seem to be the problem, maybe this will
help.
Did some digging and found a bug report against redhat version 8 concerning
terminal codes in perldoc output.
There were comments about this being a bug in groff.
https://bugzilla.redhat.com/show_bug.cgi?id=72125
