zealfire

If you can remember the high order bits then you can allocate the range of IP addresses easily. The bits are numbered as 128 - 64 - 32- 16 - 8 - 4 - 2 - 1. For understanding I'm adding all the leading 0's

Class	High Order Bits	Start	End
Class A	0 (0+0+0+0+0+0+0+0) = 0 (starting range)	0.0.0.0	127.255.255.255
Class B	10 (128+0+0+0+0+0+0+0)=128 (starting range for class B and ending for Class A)	128.0.0.0	191.255.255.255
Class C	110 (128+64+0+0+0+0+0+0) = 192 (starting range for class C and ending for Class B)	192.0.0.0	223.255.255.255
Multicast	1110 (128+64+32+0+0+0+0+0) = 224 (starting range for Multicast and ending for Class C)	224.0.0.0	239.255.255.255
Experimental	1111 (128+64+32+16+0+0+0+0) = 240 (starting range for Experimental and ending for multicast)	240.0.0.0	255.255.255.255

0.0.0.0 - default routing

zealfire

 1.  Start Regedit
   2. Go to HKEY_CURRENT_USER\ Software \ Policies \ Microsoft \ Internet Explorer \ Restrictions
   3. Add a DWORD with a name of:

NoBrowserBars       Disable changes to browsers bars.
NoBrowserClose       Disable the option of closing Internet Explorer.
NoBrowserContextMenu       Disable right-click context menu.
NoBrowserOptions       Disable the Tools / Internet Options menu.
NoBrowserSaveAs       Disable the ability to Save As
NoFavorites       Disable the Favorites.

zealfire

https://www.technipages.com/prevent-users-from-running-certain-programs

zealfire

https://docs.microsoft.com/en-us/powershell/wmf/5.1/install-configure

zealfire

Double hashing can be done using :
(hash1(key) + i * hash2(key)) % TABLE_SIZE
Here hash1() and hash2() are hash functions and TABLE_SIZE
is size of hash table.
(We repeat by increasing i when collision occurs)
First hash function is typically hash1(key) = key % TABLE_SIZE

A popular second hash function is : hash2(key) = PRIME – (key % PRIME) where PRIME is a prime smaller than the TABLE_SIZE.

zealfire

hdiutil create -fs HFS+ -srcfolder "$1" -volname "$2" "$2.dmg"

zealfire

wmic qfe list full

zealfire

Hyper-Threading
Strictly speaking, only one thread can be served by one core at a time. So if a CPU is a dual core, then supposedly only two threads can be served simultaneously. However, Intel has a technology called Hyper-Threading. This enables a single core to serve multiple threads.

For instance, a Core i3, which is only a dual core, can actually serve two threads per core. In other words, a total of four threads can run simultaneously. Thus, even if Core i5 processors are quad cores, since they don’t support Hyper-Threading (again, except the i5-4570T) the number of threads they can serve at the same time is just about equal to those of their Core i3 counterparts.

This is one of the many reasons why Core i7 processors are the creme de la creme. Not only are they quad cores, they also support Hyper-Threading. Thus, a total of eight threads can run on them at the same time. Combine that with 8MB of cache and Intel Turbo Boost Technology, which all of them have, and you’ll see what sets the Core i7 apart

zealfire

LDAP injection is a type of attack on a web application where hackers place code in a user input field in an attempt to gain unauthorized access or information. Like Java SQL injection or .NET SQL injection, an LDAP injection can lead to information theft, browser or session hijacking, defacement of website and worse.

In LDAP injection uses client-supplied data in LDAP (Lightweight Directory Access Protocol) statements without removing potentially harmful code from the request. When a web application doesn’t adequately sanitize user-supplied input, hackers may be able to change the construction of an LDAP statement which will run with the same permissions as the component that executed the command. An LDAP injection can result in serious security issues if the permissions grant the rights to query, modify or remove anything inside the LDAP tree.

For example, attackers might use an LDAP injection to insert malicious code that allows them to see all the usernames and passwords assigned to a system or to add t

zealfire

https://support.microsoft.com/en-us/help/4072698/windows-server-guidance-to-protect-against-the-speculative-execution
https://support.microsoft.com/en-us/help/4074629/understanding-the-output-of-get-speculationcontrolsettings-powershell
https://support.microsoft.com/en-us/help/4073119/protect-against-speculative-execution-side-channel-vulnerabilities-in
Will be adding more ...