Comments on: Accessing kernel objects in other sessions part 2 http://www.remkoweijnen.nl/blog/2009/02/03/accessing-kernel-objects-in-other-sessions-part-2/ About Terminal Server, Citrix, Delphi and other stuff Tue, 24 Jan 2012 22:30:12 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: daNILhttp://www.remkoweijnen.nl/blog/2009/02/03/accessing-kernel-objects-in-other-sessions-part-2/comment-page-1/#comment-828 daNIL Mon, 09 Feb 2009 09:07:51 +0000 http://www.remkoweijnen.nl/blog/2009/02/03/accessing-kernel-objects-in-other-sessions-part-2/#comment-828 Yes, you're correct. You can treat the objects and prefixes just like files and directories. Unfortunately, win32 api doesn't provide a way for enumerating them, so it doesn't make sense if you would modify your object name, or move it into other directory. I think the most useful info is that you can create the objects with the same name on different session, and access them from any other session. Yes, you’re correct. You can treat the objects and prefixes just like files and directories. Unfortunately, win32 api doesn’t provide a way for enumerating them, so it doesn’t make sense if you would modify your object name, or move it into other directory. I think the most useful info is that you can create the objects with the same name on different session, and access them from any other session.

]]> By: Cd-MaNhttp://www.remkoweijnen.nl/blog/2009/02/03/accessing-kernel-objects-in-other-sessions-part-2/comment-page-1/#comment-826 Cd-MaN Mon, 09 Feb 2009 08:31:08 +0000 http://www.remkoweijnen.nl/blog/2009/02/03/accessing-kernel-objects-in-other-sessions-part-2/#comment-826 > So if you want to hide your object, but still share it with someone else, you can use it.If I understand correctly, this is "security by obscurity"? Ie. you are creating the object in an unexpected location, but if someone else did know the location, could still access it? Isn't this equivalent with appending an arbitrary suffix to your object which is know to both parties? (Ie, instead of MyAppEvent you would create MyAppEvent.31337) > So if you want to hide your object, but still share it with someone else, you can use it.

If I understand correctly, this is “security by obscurity”? Ie. you are creating the object in an unexpected location, but if someone else did know the location, could still access it? Isn’t this equivalent with appending an arbitrary suffix to your object which is know to both parties? (Ie, instead of MyAppEvent you would create MyAppEvent.31337)

]]>