On 7 April 2010 19:18, Niki Kovacs contact@kikinovak.net wrote:
Well, it works.
Amazing! So as a malicious employee, all I have to do is run a DHCP server that dishes out host names with the adress leases and then AD will be ruined as DNS records will be wrong and computers won't match their accounts in AD?
On Wed, 7 Apr 2010, James Bensley wrote:
On 7 April 2010 19:18, Niki Kovacs contact@kikinovak.net wrote:
Well, it works.
Amazing! So as a malicious employee, all I have to do is run a DHCP server that dishes out host names with the adress leases and then AD will be ruined as DNS records will be wrong and computers won't match their accounts in AD?
What do techniques and misconfigurations in securing Windows AD servers have to do with centos?
Can this move elsewhere please?
-- Russ herrold
Amazing! So as a malicious employee, all I have to do is run a DHCP server that dishes out host names with the adress leases and then AD will be ruined as DNS records will be wrong and computers won't match their accounts in AD?
Of course not for cripes sakes, the op doesn't realize his windows xp box was named as per the hostname he desires, its merely the DNS suffix that can be assigned, ad would break if the hostname changed...
Amazing! So as a malicious employee, all I have to do is run a DHCP server that dishes out host names with the adress leases and then AD will be ruined as DNS records will be wrong and computers won't match their accounts in AD?
Boxes that are members of an AD will not accept leases from a dhcp server that has not been authorized as a dhcp server in the AD.
This setup is for a home network of stand-alone boxes.
And at the end of the article, they are also leasing addresses to Linux boxes and checking whether they are successful in the dhclient-ethX.leases file.