I find it silly how many places legacy versions are hard coded for compatibility.
1,769 karma · joined November 6, 2013
I find it silly how many places legacy versions are hard coded for compatibility.
It’d be a pleasure to see a version for 1.3, but not all Maintained SSL libraries implement it yet, https://github.com/ARMmbed/mbedtls/issues/508 mbedTLS tls for example appears not to have it landed. This is one library often used in IoT environments
(Yet Roku and more do.)
The JS engines are different though
More on theory and overall goals than "here's how you use SELinux"
i think it will be good cause the old guys were mis managing
In what ways?
I know several 3rd party developers that were just begging for the opportunity to talk to anybody in the organization about how they could configure there software to have the least impact possible on Ancestry, and they wouldn't reply. And then one day they sent a Cease and Desist order, which alienated thousands of customers who relied on those 3rd party apps. Stuff like that. Nobody listens there.
ah the totally "This is our IP, you can't use it" vs "This is a sales opportunity" mindset.
it's worse than that, they just didn't care.. and then they tried to sell themselves and wanted to minimize costs, and blamed 3rd party guys for how backed up their servers were and bad mouthed them. Tried to make themselves look more profitable than they are bad culture thing. almost a monopoly and it's a reputable private equity place - not some vulture company somebody that will come in and challenge their business model but not tell them how to run their business
This is how bitcoin works. You send value to somewhere else of your will. There is no outside party here.
I can also expect space photographers complaining even more going forward.
Avoiding side channels and valuing small code size can result in some really funky work arounds. For example, using a whole ECDH key exchange in a JavaCard co-processor in order to do EC point calculations. As seen in [1] slide 30.
[1]: https://www.blackhat.com/docs/us-17/thursday/us-17-Mavroudis...
OpenSSL and it's forks expose the primitives directly, but as is the usual advice, don't roll your own crypto and say "We're using RSA 2048" because you copied an example from stack overflow without padding.
https://intellijobs.ai/job/IBMCloud-Native-Infrastructure-En...
My own opinion, but software APIs change over the years, experience from 8 years ago may not be relevant for a product with the same name.
Never ever do I do this for tables / entities or controllers. Things get fragile fast with that.