Is remote desktop connection affected by security DLL functions in Windows?

  • Thread starter Thread starter phylotree
  • Start date Start date
  • Tags Tags
    Connection Desktop
Join the discussion
Ask a follow-up here, or get your own question answered by working scientists, mathematicians and engineers — people, not an autocomplete.
Real named experts · corrections over time · the nuance an AI answer skips
1 reply · 3K views
phylotree
Messages
48
Reaction score
2
A popular remote desktop connection issue at present shows up in my head making me wonder whether or not what I am thinking is correct at all. I am a Windows internals novice so please be prepared with my ignorance.
For security reason I suppose later versions of Windows (post-XP) have been equipped with security dll functions included to turn off all activities available on the computer that is to be monitored. Therefore the currently logged on user of that computer will be logged off automatically when the connection is done. The included dlls that act as a firewall for remote connection I think are "stuck" on purpose with the OS kernel. However since Microsoft Windows is notorious for security leaks (likely to be by chance, on purpose or even real attacks from competitors o:)), there are still software that can intercept this cohesiveness and one of its module interface was implemented to perform as if the mentioned security dlls malfunctioned or were non-existing. The connection is thus not only easier and faster but the automatic log-off function is successfully eliminated. Is this real ? My take on this is that the current user must log off and that computer must be on for the remote assistance to work.
 
Physics news on Phys.org
Could you try to be a little more... clear? A firewall cannot be a dymanic linked library, for example (because DLLs don't control network traffic).