[Bug 358261] Re: net rpc command potentially dangerous on Windows 2003 Server

2009-04-09 Thread Thierry Carrez
It's consistent with how Windows tools work. By design, you can join as many times as you want, and as long as you give it a Domain Admin password it will overwrite the existing objects in AD (without any warning). So I'd say the tools behave like they should. I understand that the process is erro

[Bug 358261] Re: net rpc command potentially dangerous on Windows 2003 Server

2009-04-09 Thread therebel22
I finally have made the test 2 times whith "net ads join" : r...@...: net ads join -U Administrateur -S dc Joined '...' to realm 'realm' r...@...: net ads join -U Administrateur -S dc Joined '...' to realm 'realm' With "net rpc join", 2 times : r...@...: net rpc join -U Administrateur -S dc Join

[Bug 358261] Re: net rpc command potentially dangerous on Windows 2003 Server

2009-04-09 Thread therebel22
Sorry, i can't test it anymore. I haven't any test DC and my windows admin don't want me to test it again on production DC .. If anybody can .. -- net rpc command potentially dangerous on Windows 2003 Server https://bugs.launchpad.net/bugs/358261 You received this bug notification because you ar

[Bug 358261] Re: net rpc command potentially dangerous on Windows 2003 Server

2009-04-09 Thread Thierry Carrez
It's by design that you can replace an existing object machine. The DC should probably protect itself against overwriting itself. What happens if you run "net ads join" instead of "net rpc join" ? Does it refuse to overwrite the existing DC machine object ? Could you post the output of both comman