How did $40m of fraudulent spending go unchecked for literally years? It seems to be that even at the largest private sector organizations this kind of malfeasance would have been caught much sooner.
198 karma · joined June 30, 2010
How did $40m of fraudulent spending go unchecked for literally years? It seems to be that even at the largest private sector organizations this kind of malfeasance would have been caught much sooner.
I see this as a strict improvement for adoption of Linux workstations in the corporate world
Are there any viable alternatives to Kubernetes and Nomad?
Seems to me that they have no choice but to hard fork off of the last Apache-licensed release of Elasticsearch et al
This is patently false. The Securities and Exchange Commission accredits and oversees all national SROs.
In fact California specifically does not tax ex-residents for income arising from the disposition of stock acquired with ISOs, which is usually the way pre-IPO employees acquire shares. This is true even if the ISOs were granted for work performed in California.
Hardware offload of a network protocol is an extremely generic concept and this patent seems to describe that concept (without any kind of novel mechanism or implementation details).
Intel has already filed (in 2019) for a European patent that seems to claim inventorship of the generic concept of hardware offloading (as it applies to QUIC)
https://data.epo.org/publication-server/pdf-document?pn=3541...
Would you feel any differently about the value of this bug if it affected, e.g. Google or Facebook?
Willing to pay a modest premium, even.
AGPL requires network-accessible code to be disclosed & licensed under an AGPL-compatible license.
The Commons Clause license outright prohibits SaaS-style offerings of the licensed code.
A lot of startups licensing their code under AGPL might still have AWS et al. eat their lunch, becuase all Amazon needs to do to remain compliant is to publish any modifications made to the AGPL-ed code.
AES-CBC requires a random IV to be used as a nonce on a per-message basis, otherwise the entire scheme breaks. The toy example given on this website uses the deprecated Node.js createCipher [2] API which does not take such an IV. In fact, the docs and runtime even warn that using CBC mode with the createCipher API is dangerous!
As the code is currently written, an attacker observing multiple encrypted messages under the same key could probably decrypt all messages!
[1] https://projects.lukehaas.me/runjs/images/runjs3.png
[2] https://nodejs.org/api/crypto.html#crypto_crypto_createciphe...
Could someone explain why this is a good move in spite of the risk that Amazon could jack their prices up in the future?
[1] http://www.business.ca.gov/StartaBusiness/AdministeringEmplo...