From 511ebaa4e808e07fcdfc5ef8a41a4b7d64fa65c6 Mon Sep 17 00:00:00 2001
From: Peter Palfrader <peter@palfrader.org>
Date: Fri, 20 Sep 2013 08:57:04 +0200
Subject: [PATCH] Mention the DisableDebuggerAttachment setting next to the
ulimit -c line in /etc/default/tor (closes: #723801)
---
debian/changelog | 2 ++
debian/tor.default | 5 +++--
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index e90dc0f2af..83519a5462 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,8 @@ tor (0.2.4.17-rc-2) UNRELEASED; urgency=low
* Re-add a few 'exit 1' statements on errors that got lost while
updating the init script to fancy LSB style output (closes: #722153).
+ * Mention the DisableDebuggerAttachment setting next to the ulimit -c
+ line in /etc/default/tor (closes: #723801).
-- Peter Palfrader <weasel@debian.org> Sun, 08 Sep 2013 16:49:04 +0200
diff --git a/debian/tor.default b/debian/tor.default
index 68c063437b..930170801f 100644
--- a/debian/tor.default
+++ b/debian/tor.default
@@ -34,8 +34,9 @@ RUN_DAEMON="yes"
# ARGS="$ARGS "
#
-# Uncomment the ulimit call below if you want tor to produce coredumps on
-# segfaults and assert errors.
+# Uncomment the ulimit call below, and set "DisableDebuggerAttachment 0"
+# in /etc/tor/torrc, if you want tor to produce coredumps on segfaults
+# and assert errors.
#
# Keeping coredumps around is some sort of security issue since they
# may leak session keys, sensitive client data and more, should such
--
GitLab