public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] CGI.pm testing needed on non-x86 arch's
Date: Wed, 23 Jul 2003 06:32:49 -0400	[thread overview]
Message-ID: <20030723103249.GA1855@enki.datanode.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 598 bytes --]

There is a security fix in the newer dev-perl/CGI for cross site
scripting vulnerability. Can I get confirmation on other arch's that it
installs fine? I expect no problems in compilation/execution, but I'd
like confirmation before unmasking it. Thanks!

-- 


-----o()o---------------------------------------------
              |  http://www.gentoo.org/
              |  #gentoo-dev  on irc.freenode.net
Gentoo Dev    |  #gentoo-perl on irc.freenode.net
Perl Guy      |
              |  GnuPG Key ID:       AB5CED4E9E7F4E2E
-----o()o---------------------------------------------


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-07-23 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 10:32 Michael Cummings [this message]
2003-07-23 18:11 ` [gentoo-dev] CGI.pm testing needed on non-x86 arch's Lars Weiler
2003-07-24  2:25 ` Aron Griffis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030723103249.GA1855@enki.datanode.net \
    --to=mcummings@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox