summaryrefslogtreecommitdiff
path: root/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'open_issues/libmachuser_libhurduser_rpc_stubs.mdwn')
-rw-r--r--open_issues/libmachuser_libhurduser_rpc_stubs.mdwn14
1 files changed, 13 insertions, 1 deletions
diff --git a/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn b/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
index 80fe36f8..670c82cb 100644
--- a/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
+++ b/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2010, 2011, 2012 Free Software Foundation,
+[[!meta copyright="Copyright © 2010, 2011, 2012, 2013 Free Software Foundation,
Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -121,3 +121,15 @@ License|/fdl]]."]]"""]]
libmachuser and libhurduser? should they be linked to explicitly, or
assume libc brings them?
<braunr> pinotree: libc should bring them
+
+
+# IRC, freenode, #hurd, 2013-02-25
+
+ <braunr> we should also discuss the mach_debug interface some day
+ <braunr> it's not exported by libc, but the kernel provides it
+ <braunr> slabinfo depends on it, and i'd like to include it in the hurd
+ <braunr> but i don't know what kind of security problems giving access to
+ mach_debug RPCs would create
+ <braunr> (imo, the mach_debug interface should be adjusted to be used with
+ privileged ports only)
+ <braunr> (well, maybe not all mach_debug RPCs)