New version + Numerous Use of qw(...) as parentheses is deprecated messages

Bug #991869 reported by Emite Aves
272
This bug affects 4 people
Affects Status Importance Assigned to Milestone
psad (Debian)
Fix Released
Unknown
psad (Fedora)
Won't Fix
Medium
psad (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Description of problem:
Due to a change in perl syntax for Perl 5.14 and onwards, the use of qw(...) in
specific contexts is now disallowed. This generates lots of messages of the
form:
Starting Port Scan Attack Detector: psad Use of qw(...) as parentheses is
deprecated at /usr/sbin/psad line 4264.
Use of qw(...) as parentheses is deprecated at /usr/sbin/psad line 4432.
Use of qw(...) as parentheses is deprecated at /usr/sbin/psad line 5106.
Use of qw(...) as parentheses is deprecated at /usr/sbin/psad line 6615.
[...]

A fix is available in the psad-2.2 released Apr 20, 2012.

Source tar archive (.gz)
http://cipherdyne.org/psad/download/psad-2.2.tar.gz

Changelog
http://cipherdyne.org/cgi-bin/gitweb.cgi?p=psad.git;a=blob_plain;f=ChangeLog;hb=refs/heads/psad-2.2

Kind regards,

Emite Aves

Tags: psad python
Revision history for this message
In , Frank (frank-redhat-bugs) wrote :

Description of problem:
Due to a change in perl syntax for Perl 5.14 and onwards, the use of qw(...) in specific contexts is now disallowed. This generates lots of messages of the form:
Use of qw(...) as parentheses is deprecated at /usr/sbin/psad line 4264.

Version-Release number of selected component (if applicable):
psad-2.1.7-2.fc15.x86_64
perl-5.14.2-191.fc16.x86_64

How reproducible:
100% of time

Steps to Reproduce:
1. Run "psad --help" or any other psad options.
2.
3.

Actual results:
Numerous messages about deprecated feature.

Expected results:
No deprecated messages

Additional info:
Reading some of the perl list this only occurs in statements of the form:
for my $var qw(...) { ... }
and is fixed by the addition of "()", i.e.
for my $var (qw(...)) { ... }

Revision history for this message
In , Šimon (imon-redhat-bugs) wrote :

This has been fixed in upstream e013ca6230a6210ac6e405da08df370fb4818831.

It might be included in the upcoming psad-3.0 release.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

psad-2.1.7-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/psad-2.1.7-5.fc16

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Package psad-2.1.7-5.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing psad-2.1.7-5.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1625/psad-2.1.7-5.fc16
then log in and leave karma (feedback).

Changed in psad (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in psad (Ubuntu):
status: New → Confirmed
Changed in psad (Debian):
status: New → Fix Released
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 16 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
FR. Loïc (hackurx) wrote :

Please correct this bug quickly in Ubuntu 12.04 LTS because now it offers no protection.

Regards.

information type: Public → Public Security
Changed in psad (Fedora):
importance: Unknown → Medium
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.