Muftasoft TM

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Cracking Windows ======


[[https://www.youtube.com/watch?v=3ytqP1QvhUc|let’s play with a ZERO-DAY vulnerability “follina”
]]


[[https://www.bleepingcomputer.com/news/security/fake-windows-exploits-target-infosec-community-with-cobalt-strike/|
Fake Windows exploits target infosec community with Cobalt Strike
]]

[[https://www.youtube.com/watch?v=dK6E-c2x9EE|
Cobalt Strike Custom Profile Attack With .LNK Exploit VS Windows Defender 11 With Custom UAC Bypass.
]]


[[https://businessinsights.bitdefender.com/technical-advisory-cve-2022-30190-zero-day-vulnerability-follina-in-microsoft-support-diagnostic-tool|
Technical Advisory: CVE-2022-30190 Zero-day Vulnerability “Follina” in Microsoft Support Diagnostic Tool]]

[[https://null-byte.wonderhowto.com/how-to/hacking-windows-10-intercept-decrypt-windows-passwords-local-network-0184536/|How to Intercept & Decrypt Windows Passwords on a Local Network]]

[[http://linux-training.be/networking/ch23.html|Chapter 23. samba domain controller
]]


[[https://www.oreilly.com/openbook/samba/book/ch05_01.html|5. Browsing and Advanced Disk Shares
]]

Finally, Windows NT servers serving as primary domain controllers contain a sneak that allows them to assume the role of the local master browser in certain conditions; this is called the preferred master browser bit. Earlier, we mentioned that Samba could set this bit on itself as well. You can enable it with the preferred master option:


#  Browsing election options
os level = 33
local master = yes
preferred master = yes
If the preferred master bit is set, the machine will force a browsing election at startup. Of course, this is needed only if you set the os level option to match the Windows NT machine. We recommend that you don't use this option if another machine also has the role of preferred master, such as an NT server.

5.1.4 Domain Master Browser
In the opening chapter, we mentioned that in order for a Windows workgroup or domain to extend into multiple subnets, one machine would have to take the role of the domain master browser. The domain master browser propagates browse lists across each of the subnets in the workgroup. This works because each local master browser periodically synchronizes its browse list with the domain master browser. During this synchronization, the local master browser passes on any server that the domain master browser does not have in its browse list, and vice versa. In a perfect world, each local master browser would eventually have the browse list for the entire domain.

Unlike the local master browser, there is no election to determine which machine assumes the role of the domain master browser. Instead, the administrator has to set it manually. By Microsoft design, however, the domain master browser and the primary domain controller (PDC) both register a resource type of <1B>, so the roles - and the machines - are inseparable.

If you have a Windows NT server on the network acting as a PDC, we recommend that you do not use Samba to become the domain master browser. The reverse is true as well: if Samba is taking on the responsibilities of a PDC, we recommend making it the domain master browser as well. Although it is possible to split the roles with Samba, this is not a good idea. Using two different machines to serve as the PDC and the domain master browser can cause random errors to occur on a Windows workgroup.