12%
10.06.2015
, and public key encryption algorithms (Table 2). OpenSSL really focuses on encryption and decryption and not compression. Consequently, you shouldn't expect the encrypted file to be smaller than the original
12%
10.06.2015
not uneventful: Changes made under HKEY_CURRENT_USER are stored, as expected, under HKCU in Software\Microsoft\AppV\Client. App-V does not save these changes itself, however; instead, it relies on the operating
12%
09.08.2015
a single SSD speak for themselves. You can expect write IOPS hits in both RAID 5 and RAID 1. If you are thinking of purchasing a large number of SSDs and would like to achieve balanced performance
12%
20.05.2014
-EX processors (480 logical cores) and more than 10TB of memory are expected to hit the market before the end of 2014. NUMA optimization will be critical on such servers, because they will have more than two NUMA
12%
11.06.2014
://localhost/repositories/index.html -o /dev/null
200 http://localhost/repositories/index.html
Voilà, the directory is protected, and everything works as expected.
The web server configuration file has a few special features
12%
11.10.2016
written in Python greatly improves the cross-platform capability.
Even though Editra (Figure 6) is in development, it has a large number of features you would expect from a more mature editor, including
12%
13.02.2017
run -d --read-only chrisbinnie/my-web-server
As you might expect, this launches a container to which you cannot write in any way, shape, or form. In other words, if your container is attacked
12%
14.03.2018
. When creating a subnet, you can specify that every VM you connect to this network is assigned a public IP automatically.
AWS stores routes in routing tables as expected, and administrators maintain
12%
14.11.2013
of information about memory errors. Normally, you wouldn't expect memory errors, either correctable or uncorrectable, to occur very often. However, as a good administrator, you should periodically scan your
12%
05.08.2024
(Figure 2). Many production Kubernetes workloads don't implement TLS at the pod level, expecting the cluster traffic to be secured automatically, but don't take that outcome for granted
