Bug 204066 - wireshark doesn't work as non root user
Summary: wireshark doesn't work as non root user
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: wireshark
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Radek Vokál
QA Contact:
URL: http://bugs.centos.org/view.php?id=1459
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-25 11:57 UTC by Johnny Hughes
Modified: 2007-11-30 22:07 UTC (History)
4 users (show)

Fixed In Version: RHSA-2006-0658
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-12 15:41:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0658 0 normal SHIPPED_LIVE Low: wireshark security update 2006-09-12 04:00:00 UTC

Description Johnny Hughes 2006-08-25 11:57:29 UTC
Description of problem:  Wireshark does not run as a non root user ... also
there is no wireshark "component" to select on the RedHat bugzilla.

Version-Release number of selected component (if applicable): wireshark-0.99.2-EL4.1

How reproducible: always

Steps to Reproduce:
1. Run wireshark as a non-root user and start a capture

We found this issue in CentOS-4.4 and then verified that it also exists in RHEL-4u4.

The problem is that the /etc/pam.d/wireshark is incorrect.

The pam.d file from ethereal used for wireshark fixes the problem.

See this link for more details:

http://bugs.centos.org/view.php?id=1459

Comment 4 Red Hat Bugzilla 2006-09-12 15:41:37 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0658.html



Note You need to log in before you can comment on or make changes to this bug.