Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #19759
Closed (moved) (moved)
Open
Created Jul 27, 2016 by Trac@tracbot

systemd tor.service hardening: add MemoryDenyWriteExecute=true

In systemd 231, the MemoryDenyWriteExecute option was added:

      A new service setting MemoryDenyWriteExecute= has been added, taking
      a boolean value. If turned on, a service may no longer create memory
      mappings that are writable and executable at the same time. This
      enhances security for services where this is enabled as it becomes
      harder to dynamically write and then execute memory in exploited
      service processes. This option has been enabled for all of systemd's
      own long-running services.

https://lists.freedesktop.org/archives/systemd-devel/2016-July/037220.html

Can you please add:

MemoryDenyWriteExecute=true

to https://gitweb.torproject.org/tor.git/tree/contrib/dist/tor.service.in in the [Service] section?

Note that systemd < 231 will simply ignore this unknown option so there is no backwards compatibility concern.

Trac:
Username: candrews

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking