From 088ca85671518ac9033904dae6444d7d532586d4 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 22 Jul 2011 09:41:11 +0200 Subject: IRC. --- hurd/translator/procfs/jkoenig/discussion.mdwn | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) (limited to 'hurd') diff --git a/hurd/translator/procfs/jkoenig/discussion.mdwn b/hurd/translator/procfs/jkoenig/discussion.mdwn index b66af7de..64e3776e 100644 --- a/hurd/translator/procfs/jkoenig/discussion.mdwn +++ b/hurd/translator/procfs/jkoenig/discussion.mdwn @@ -166,3 +166,21 @@ IRC, freenode, #hurd, 2011-03-28 mentoring the previous procfs implementation (though I never got around to look at his buggy code...) ok + +IRC, freenode, #hurd, 2011-07-22 + + hm, why /proc/$pid/stat is 600 instead of 644 of linux? + pinotree, it reveals information which, while not that sensitive, + would not be available to users through the normal proc interface. + (it's available through the ps command which is setuid root) + we discussed at some point making it 644, IIRC. + hm, then why is it not a problem on eg linux? + (btw you can change it with the -s option.) + pinotree, it's not a problem because the information is not that + sensitive, but when rewriting procfs I preferred to play it self and + consider it's not procfs' job to decide what is sensitive or not. + IIRC it's not sensitive but you need the task port to query it. + like, thread times or something. + status is 644 though + but status contains information which anyone can ask to the proc + server anyway, I think. -- cgit v1.2.3