30 karma · joined August 1, 2014
A node.js module which implements a standard API for symmetric encryption and does so by providing the requisite key derivation from a supplied secret, strong key and cipher selections, performs validate then decrypt of cipher text while supporting most language character sets and ASN.1 encoding ensuring compatibility with most if not all database engines.
Used best practices documentation and am currently using famous cryptographers throughout history to name each release.
Example: v3.0.4 Étienne Bazeries - He is best known for developing the "Bazeries Cylinder", and is described as "one of the greatest natural cryptanalysts the science has seen".
The NIST SP 800 series publications were paid for by our tax money and outline how encryption should be used for ALL. Not to mention sets standards for all of the intricacies that come with development, implementation and validation of strong algorithms for use in commerce, medical, federal, military and even GAH personal use.
If you wish you could go install a docker image for a honeypot and then build policies with selinux to confirm yourself.
When policies and environments are setup correctly it can and will help protect the system.
Scenario: The target; A DMZ, forward facing system running an application such as Apache.
A zero day exists in the apache service that allows code execution as the running user; say apache for example.
If care has been taken with an selinux policy that prevents the apache user from executing anything but the shared libraries and binaries associated with the apache web service then an attacker that gained access as the apache user would not be able to escalate privileges or engage in further local attacks on the system due to the policy constraints.
Resources: The URI https://www.serverlab.ca/tutorials/linux/web-servers-linux/c... provides some exmaples for apache however the following URI https://access.redhat.com/documentation/en-us/red_hat_enterp... (see procedure 3.2 & 3.3) for details on using selinux to confine processes and users.
1. Late 90's/Early 2000's, Microsoft's implementation and inclusion of CDRW/DVDRW functionality native to the OS eliminating competition from smaller companies that had pioneered the technology and was selling their software to Windows desktop users.
2. Late 90's/Early 2000's, Microsoft's implementation and development of Active Directory which not only rivaled Novell's Netware flagship product but also went against RFC's put forth by the larger community that rivaled OpenLDAP. Because of the desktop shares and users already on the Windows NT platform put thousands out of work and nearly put Novell out of business.
3. Early to mid 2000's, Microsoft moves away from already found vulnerable MSCHAP, MSCHAPV2 authentication protocols in favor of the MIT Kerberos protocol for all network authentication of users and systems in Active Directory.
Not only did this put those companies out to pasture and eliminate a large amount of revenue but the idea of stealing and idea is very bad tact. Reverse engineering code to gain a larger market share is not only dishonest but plagarism and illegal in schools. Why should the free economy play by a different set of rules?
People wonder why Microsoft has a bad reputation, the three things I have witnessed over the years in conjunction with the snatching up smaller companies and parting them out make me and I am sure many others very skeptical of their desire to snatch up the worlds largest source code repository.
Having watched Microsoft over the years steal ideas from smaller companies (not purchase them then bastardize and part them out mind you), but actually steal their ideas and make them standard in their operating system.
Some examples are CDR/CDRW now standard after small companies in the late 90's developing the standard.
The bastardized implementation of Active Directory after Novell's Netware platform and the later implementations of OpenLDAP and the standards that were spurned.
What about the MIT Kerberos authentication mechanisms after Microsofts MsCHAPv2, MsCHAP & NTLM roll your own crypto schemes were found easily crackable and exploitable?
I can go on but actually have to do some work today...