Microsoft security best practices is never to name anything .db They
recommend obfuscating the function of the file and putting some strange or
random (.bob) file extension. This is for when you have an active
intrusion, you are not handing them what to take on a silver platter. You
could argue
I assume nothing in the Server logs for security and applications at the
corresponding time?
-Original Message-
The environment is Windows Server 2012 R2, with the database on a local NTFS
drive.
"Several operating systems include arc4random, an API originating in OpenBSD
providing access to a random number generator originally based on RC4. In
OpenBSD 5.5, released in May 2014, arc4random was modified to use
ChaCha20.[11][12] As of January 2015, implementation of arc4random in
NetBSD[13][1
Have you found yourself in an ITAR mess?
https://en.wikipedia.org/wiki/Export_of_cryptography_from_the_United_States
The length of the keys is usually the determining factor for EAR. I'm not
an expert, but I'm guessing that is why they are concerned.
-Original Message-
From: sqlite-users
4 matches
Mail list logo