| Summary: | Propose that you turn on PrivateTmp=true in service file for dhcpd | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Daniel Walsh <dwalsh> |
| Component: | dhcp | Assignee: | Jiri Popelka <jpopelka> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | jpopelka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-17 17:23:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 782466 | ||
|
Description
Daniel Walsh
2012-01-17 15:39:30 UTC
Actually it's only dhclient (dhclient-script) that uses /tmp. There's a code in dhcpd that reads attributes of files in /tmp to generate semi random data, but it doesn't seem to be used anyway. So I'm going to revert the change I already did and close this as NOTABUG. Well do any of the scripts to redirection within bash command << _EOF ... _EOF Also can't dhclient-script execute custom scripts? (In reply to comment #2) > Well do any of the scripts to redirection within bash > > command << _EOF > ... > _EOF Not sure whether this is what you are asking (if that was a question), but dhclient-script uses /tmp this way: rscf="$(mktemp ${TMPDIR:-/tmp}/XXXXXX)" echo "nameserver ${nameserver}" >> ${rscf} change_resolv_conf ${rscf} rm -f ${rscf} change_resolv_conf is from /etc/sysconfig/network-scripts/network-functions and for example /etc/sysconfig/network-scripts/ifup-post use it the same way. > Also can't dhclient-script execute custom scripts? Yes, it runs (if they exist) /etc/dhcp/dhclient-enter-hooks /etc/dhcp/dhclient-up-hooks /etc/dhcp/dhclient-down-hooks /etc/dhcp/dhclient-exit-hooks /etc/dhcp/dhclient.d/*.sh So why not be secure by default and not have to worry about users hacking something in here to break dhclient or get a privledge exploit? I'm not sure I understand. There's no dhclient systemd unit to put PrivateTmp into. dhclient is started either by NetworkManager (NM) or by network-scripts. And in case of NM the dhclient-script is even not used because NM has its own "script" for dhclient. I thought I checked that it is had a systemd unit file. Sorry never mind. |