557 karma · joined February 13, 2010
1. Build work experience for your resume 2. Develop expertise with the software that the project uses and produces 3. Generate ideas for your own startup 4. Meet and interact with prospective customers for your own startup, or prospective coworkers at other startups where you might like to work
Do that for 6 months or a year, and then try applying to startups which use that open source project (or start your own business solving a common problem that users run into with that project).
- manufacturers must tell customers up front about the lifespan of security patches and updates - manufacturers must provide a public point of contact for vulnerability disclosure
* https://mvsp.dev/mvsp.en/index.html * https://www.goldfiglabs.com/guide/saas-cto-security-checklis... * https://latacora.micro.blog/2020/03/12/the-soc-starting.html
If there's an NFT that says you're the owner of a fancy bottle of wine stored in some wine vault somewhere, you'll never sniff that wine unless the proprietor of the vault agrees you own it and is willing to surrender it to you. If an NFT says you own 5 bushels of lettuce on a truck headed out of Walla Walla, you'll never see those bushels unless the trucking company agrees you own the lettuce and is willing to deliver it to your care. If an NFT says you own a hilarious GIF hosted somewhere on the Internet, you'll never gaze upon it unless that hosting service agrees to serve it to you.
If I scribbled on the back of a napkin that I was transferring my immortal soul to you, could you redeem that napkin for my soul? Would it make a difference if I put the deed on the blockchain? I would say the only differences between the napkin and the blockchain are 1) anyone can see it on the blockchain; 2) on the blockchain the deed can't be tampered with later; 3) the blockchain can include some programmatic constraints/triggers on the transaction (eg to make sure I can only sell my soul once, I can only sell my own soul, I'm now flagged as doomed to wander the earth in eternal torment, etc).
Not too many breaking changes per-se, but lots of old API calls deprecated (pretty much all the old low-level APIs), plus new default values for a variety of things.
Also, going forward they'll be using the standard semantic version-numbering system.
I don't see anything new, but nice to have their official position in a compact FAQ format. Also, I think the headline of this MSN article (as well as the Register article from which it seems to be copied) is somewhat misleading -- the NSA doesn't seem to be suggesting they think quantum computers will _never_ be able to break public-key encryption, just that everyone should sit tight and trust the ongoing NIST process for standardizing post-quantum crypto:
> Once NIST post-quantum cryptographic standards are published and certification procedures for those algorithms are established, CNSSP-15 [US gov standard for protecting classified info] will be updated with a timeline for required use of the post-quantum algorithms and disuse of the quantum-vulnerable portion of the current CNSA Suite of algorithms.
And for the time being, adding a pre-shared key where possible to existing public-key algorithms is a better quantum-mitigation strategy than trying to use a new, unproven alternative:
> Many commercial protocols allow a pre-shared key option that may mitigate the quantum threat, and some allow the combination of pre-shared and asymmetric keys in the same negotiation. However, this issue can be complex.... NSA considers the use of pre-shared symmetric keys in a standards-compliant fashion to be a better near-term post-quantum solution than implementation of experimental post-quantum asymmetric algorithms that may or may not be proven secure and which will not be compatible with NIST standards.
> AWS users with access to the AWS Management Console can authenticate themselves by typing in their passwords and then simply touching the MFA security token plugged into their computer’s USB port.... Customers can also use their MFA devices to safely access multiple AWS accounts, as well as other token-enabled applications, such as GitHub, Gmail, and Dropbox.
Plus, from a practical standpoint, what do you do when a site forces you to change your password because they fear their password db has been compromised (or has asinine rules about your password being too long, or make you rotate your password every 90 days, or they change their domain name 5 times in 3 years)?
CODE Technology is a small, newly-funded startup devoted to measuring the quality of medical care by collecting patient-reported outcome measures. We've got an informal, small-team vibe, and offer flexible working arrangements. We're looking to hire another "full-stack" software generalist. Our core software is a web application built with the Grails framework, so we're looking for someone good at:
* Groovy (or some other JVM language, like Java, Scala, etc)
* SQL
* HTML/JS/CSS
Even more awesome would be experience with: * Grails
* MySQL
* Linux
* AWS
* Ansible
You'll be working on a wide range of problems, like: * constructing SQL queries to find outliers in survey responses
* streamlining the web UI for entering new patients into our app
* fashioning logic to extract relevant data from customer's medical-record systems
* automating the scale up/down of front-end servers to match demand
Email justin@codetechnology.com to get started -- our relaxed interview process consists of a few hour-long chats (no brain-teaser or "write some code" questions) with our developers, an hour-long pair-programming session, and a 4-hour take-home programming sample (as the last step).We're a 3-person startup looking for developer #2. Our business is collecting patient-reported outcomes over the Web. Our platform is built on Groovy/Grails, so we're looking for a developer with experience in:
* Groovy (or some other JVM language, Java, Scala, etc)
* SQL
* HTML/JS/CSS
Email me at justin@codetechnology.com if you're interested in making a big impact at a small but rapidly growing company.http://thehill.com/blogs/hillicon-valley/technology/281309-r...
http://www.bloomberg.com/news/2013-02-08/obama-said-near-iss...
I don't think it's fair to characterize the intention of stuxnet as blowing up reactors. From what I've read, the purposeful damage it was designed to inflict was to disable uranium-enriching equipment. I don't recall reading anything about purposeful attempts to use the software to kill or wound.
That's where I'd draw the line: purposeful killing. So I'd describe this as a case of cyber-sabatoge -- not a case of cyber-war.
If your fifth year at school really is free, and you're enjoying the college experience, then there's no harm in spending another year there. You will learn a few things in your upper-level CS classes that you'll use at some point in your programming career. But there's nothing you can learn in any of your CS classes that you can't learn on your own outside of the classroom. The only real value of a CS education at a brick-and-motor university is a) being immersed in a community of academic pursuit and discourse, and b) the alumni connections. And you don't get much value from those things just by attending classes -- you have to go out and pursue those relationships with your professors, classmates, and alumni.
I'm fairly certain that's what he's talking about. A) He's Yves Lafon, and B) when you're talking web architecture, you care very much about what intermediaries can do.