Tag Info

New answers tagged

0

Do not implement both. Is useless. Using the both rule sets is a waste of CPU and memory, because both of them are overlapping. PCI Compliance require a WAF in some cases, but doesn't specify exactly the functionality. Almost all auditors will look to see if the WAF is protecting you from SQLi, XSS etc. which, in this case, any of the rule sets will do ...


1

This link gives a pretty good explanation. In particular, this section talks about how to verify packages. In a nutshell when you install packages your system check that they are signed with a known key, using public key crypto. This guarantees that the packages come from a "trusted" source. In your case some packages were signed with an unknown key and you ...


0

There is the hardware based RDRAND instruction on IvyBridge Intel processors. If that is availabe (ie chip has instuction and does not have the RDRAND hardware bug cover-up) then I think Linux does automatically use it. Meaning you should get very large amounts of true random numbers very fast.


9

Entropy is required in the following sense: if a PRNG has only n bits of entropy, then this means that it has (conceptually) only 2n possible internal states, and thus could be broken through brutal enumeration of these 2n states, provided that n is low enough for such a brute force attack to be feasible. Then things become complex, because the "entropy ...


0

I found a question and answer related to keys and group policy here ServerFault. Also, the code listed at the link is: edit the Sudo User With: %AccessGroup ALL=(git-sync) NOPASSWD: /usr/bin/"Access" and edit the hook with: sudo -u git-sync /usr/bin/"AccessGroup" push origin There are also the commands: #!/usr/sbin/setkey -f # # SPD for gateway ...


2

dev/random is not even remotely the same as NIST SP 800-90A DRGB. If you want to claim compliance to NIST SP 800-90A DRGB then hire a test lab to test your DRBG and submit the results to NIST's Cryptographic Algorithm Validation Program (http://csrc.nist.gov/groups/STM/cavp/index.html) and then it will end up on this list: ...


2

The cat ~/.ssh/authorized_keys command shows you the authorized_keys file of the currently logged in user. When logged in as root, or using sudo, this will give you the authorized_keys file of the root user. The authorized_keys file, at least on Ubuntu, is usually owned by the user. So the currently logged in user (root or not) can see it. The .ssh ...


3

If we take a look at the man page for random we get the following: The random number generator gathers environmental noise from device drivers and other sources into an entropy pool. The generator also keeps an estimate of the number of bits of noise in the entropy pool. From this entropy pool random numbers are created. At the bottom we see: ...


1

Cisco and Juniper routers implement GDOI. Also you can look at this implementation: GDOI Reference Implementation Primer, but it's a bit old.


1

I initially shared the same goal when I began considering encrypting my PC. Unfortunately, after hours and hours of research, all I learned was that VeraCrypt does not currently support encrypting Linux system drives. Ref: https://veracrypt.codeplex.com/wikipage?title=Supported%20Systems%20for%20System%20Encryption I was also not able to find an ...


2

There isn't a document like that because it is highly dependent on its application, its configuration, and its use. Linux has more configuration options which can make it faster and safer (whatever that might mean in your context), but those options also mean that it can be slower and more dangerous. If there was an "official document", then every ...


1

I've recently started to work on USBGuard which implements a USB device whitelist/blacklist with the help of UDev and the Linux kernel USB authorization feature. It's a user-space daemon that listens to UDev events and authorizes or deauthorizes USB devices based on a set of rules written in a custom rule language. I think it makes it much harder for an ...


2

Is it possible for a virus/worm to attack on your host to attack the guest OS? Yes. Is it likely? No. Malware can do anything you can do, including writing to the virtual disk. The easiest route would be to simply mount the virtual machine drive, and write new malware to it. This is unlikely because it would take specially crafted code to exploit this. ...


-1

Short Answer: Yes, both the host (in your case Windows) and the guest (in your case Linux) OS can be attacked by malware. Additional Details: In fact - with techniques like "Red Pill and Blue Pill" (like in the Matrix movie) it is possible for malware to bypass the barrier of virtualization and proliferate on the host or hypervisor. So please follow ...


2

I'd recommend Virtutech's SIMICS software. Note that Virtutech was bought by Intel and assigned to their subsidiary: Wind River. Simics is a SIMULATOR, which has important distinctions from an EMULATOR (like qemu). See http://stackoverflow.com/questions/1584617/simulator-or-emulator-what-is-the-difference for specifics on the differences. Simics simulates ...


0

You first want to set up a host OS (Windows or Kali, whichever you prefer to use when you're not hacking.) Inside that host OS, install a virtual machine platform (VMware, VirtualBox, whatever you choose.) Inside the virtual machine control panel, create a first VM and install Kali, (presuming you want to use Kali for your pentest environment.) I would ...


0

Running a kali VM provides some benefits: Restoration - It is easy to restore your machine when you mess it up. If you're playing around with security tools and/or malware, changes are good that, at some point, you will damage your operating system. Without a VM, you would have to reinstall everything from scratch; with a VM, you can save an image and ...



Top 50 recent answers are included