Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 123292 - Security Handbook Chroot rewrite
Summary: Security Handbook Chroot rewrite
Alias: None
Product: [OLD] Docs on
Classification: Unclassified
Component: Other documents (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Docs Team
Depends on:
Reported: 2006-02-18 09:22 UTC by Chris White (RETIRED)
Modified: 2007-07-04 05:45 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

shb-chroot.xml (shb-chroot.xml,9.39 KB, text/plain)
2006-02-18 09:23 UTC, Chris White (RETIRED)
shb-chroot.diff (shb-chroot.diff,11.18 KB, patch)
2006-02-18 09:23 UTC, Chris White (RETIRED)
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Chris White (RETIRED) gentoo-dev 2006-02-18 09:22:33 UTC
The security handbook chroot guide (/doc/en/security/shb-chroot.xml) tries to  use bash to explain the workings of chrooting a service.  While it's a nice intro to chrooting in general, it doesn't really touch the nitty gritty of getting services chroot'ed.  This rewrite uses a real life example service (The monkeyd webserver) to explain how to setup the chroot'ed environment.  I think it meets the purposes of the document a tad better. For those of you that REALLY want it, I'm attaching a diff ;p.
Comment 1 Chris White (RETIRED) gentoo-dev 2006-02-18 09:23:21 UTC
Created attachment 80110 [details]

The rewritten guide.
Comment 2 Chris White (RETIRED) gentoo-dev 2006-02-18 09:23:52 UTC
Created attachment 80111 [details, diff]

A diff against the original guide.
Comment 3 nm (RETIRED) gentoo-dev 2007-02-12 22:00:50 UTC
Docs-team: it's been awhile on this bug. I'm willing to add it to the guide; not a hard commit. However, do you guys think a full-up example is necessary, or is our existing minimal chroot stuff sufficient?
Comment 4 nm (RETIRED) gentoo-dev 2007-07-04 05:45:26 UTC
Right, timing out, no response in 5 months since my last query, no response in over a year. The example package in question isn't available for many arches, much less marked stable.

Too bad this became one of those bugs that just becomes irrelevant after awhile. One less thing to worry about. Closing.