From 5a99e86ad2627d1d88232d87a31c07e92e4eb22a Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Fri, 30 Jul 2010 16:30:04 +0200 Subject: hurd/debugging/rpctrace: More information. --- hurd/debugging/rpctrace.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'hurd/debugging') diff --git a/hurd/debugging/rpctrace.mdwn b/hurd/debugging/rpctrace.mdwn index ee5ee3e7..de46c08d 100644 --- a/hurd/debugging/rpctrace.mdwn +++ b/hurd/debugging/rpctrace.mdwn @@ -39,3 +39,15 @@ See `rpctrace --help` about how to use it. hm... for a funny effect, try running rpctrace on /servers/socket/1, and then use dpkg... ;-) + +* IRC, unknown channel, unknown date. + + the problem of rpctrace is that it's a man in the middle :) + so in principle, by design authentication stuff shouldn't work + I don't think the Hurd auth mechanism in any way prevents or tries to prevent man-in-the-middle... + maybe, but just try, you'll see all kinds of issue as soon as you have authentication stuff + and the basic reason is that being a man in the middle needs special care + which rpctrace doesn't completely do + it's a while since I have dived into rpctrace; but AIUI, it should work just fine if the proxying is done properly + note that there is a number of known bugs in rpctrace, for which zhengda has sent patches... though I haven't reviewed all of them I think + there are some nasty Mach operations that are really hard to proxy -- but I don't think the auth mechanism needs any of these... -- cgit v1.2.3