Bug 2683 - why not chroot named?
why not chroot named?
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
6.0
i386 Linux
low Severity medium
: ---
: ---
Assigned To: David Lawrence
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-09 10:00 EDT by Chris Ricker
Modified: 2015-09-04 16:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-05-27 13:44:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 1999-05-09 10:00:13 EDT
As shipped, named runs as root.

There's no real reason for this.  It can be easily
chrooted or at least, even more trivially, run as a
non-privileged user.

later,
chris

------- Email Received From  Chris Ricker <kaboom@gatech.edu> 05/27/99 22:49 -------
Comment 1 openshift-github-bot 2015-09-04 16:15:10 EDT
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/ca4099284d6f19b44d543d0db9640b567c934765
Issue 2683 - deprecation warning from moment.js

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