Bug 522787 - quagga: build future versions without PAM
Summary: quagga: build future versions without PAM
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: quagga
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jiri Skala
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-11 12:58 UTC by Tomas Hoger
Modified: 2014-11-09 22:32 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-09-14 12:05:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tomas Hoger 2009-09-11 12:58:40 UTC
Description of problem:
quagga packages as shipped in Fedora are built with PAM support enabled (--with-libpam) by default.  However, those PAM checks are only enforced on client-side (vtysh) and not server side, making it trivial to bypass them (via ptrace/gdb, LD_PRELOAD or custom vtysh build without PAM support).

vtysh communicates with daemons using unix sockets.  Permissions on the sockets are set as: quagga:quaggavt 660.  User needs to be either root or member of quaggavt group to communicate with the daemons.

Default PAM configuration only restricts access to root user, but once non-root user is member of quaggavt (s)he can easily bypass that restriction.

As requirement of quaggavt group membership seems fairly sufficient for access control, we should consider dropping PAM support by default, as it can only mislead users to believing there is additional check while there is none.


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