ab · Hacker News

It's more about what happens when you toss your phone into the landfill after two years, and the mountain of dead electronics starts leeching toxins into the groundwater.

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3908467/

Login.gov | REMOTE or Washington, DC | Software Engineers, Site Reliability Engineers, Security Engineers | Full-Time | https://login.gov

Login.gov gives the public simple, secure access to multiple US government services through one verified account. We're working to fix online identity for US government services.

The Login.gov team operates like a startup within the government, working in the open as a distributed, agile team. The core product is open source, hosted in modern cloud infrastructure, and built for scale. Tens of millions of people have Login.gov accounts, and we aim to be the preferred entrypoint for all government digital services. Our users include people accessing benefits, applying for government jobs, serving in the military, and collecting funds awarded through grant programs.

Find us on Github: https://github.com/18F/identity-idp

The Login.gov project began as a collaboration between 18F and the U.S. Digital Service (USDS). Today it's part of the Technology Transformation Services (TTS). You'll join other software engineers delivering better public services through modern technology.

* Ruby Software Engineer: https://join.tts.gsa.gov/join/application-engineer/

* Site Reliability Engineer: https://join.tts.gsa.gov/join/devops-engineer/

* Security Engineer: https://join.tts.gsa.gov/join/security-ops-engineer/

The above postings open on a revolving basis. If they're not open, just email us at [email protected] or [email protected], where we can answer questions and accept your application.

Feel free to reply on thread with any questions.

Login.gov | REMOTE or Washington, DC | Software Engineers, Site Reliability Engineers, Security Engineers | Full-Time | https://login.gov

Login.gov gives the public simple, secure access to multiple US government services through one verified account. We're working to fix online identity for US government services.

The Login.gov team operates like a startup within the government, working in the open as a distributed, agile team. The core product is open source, hosted in modern cloud infrastructure, and built for scale. Tens of millions of people have Login.gov accounts, and we aim to be the preferred entrypoint for all government digital services. Our users include people accessing benefits, applying for government jobs, serving in the military, and collecting funds awarded through grant programs.

Find us on Github: https://github.com/18F/identity-idp

The Login.gov project began as a collaboration between 18F and the U.S. Digital Service (USDS). Today it's part of the Technology Transformation Services (TTS). You'll join other software engineers delivering better public services through modern technology.

* Ruby Software Engineer: https://join.tts.gsa.gov/join/application-engineer/

* Site Reliability Engineer: https://join.tts.gsa.gov/join/devops-engineer/

* Security Engineer: https://join.tts.gsa.gov/join/security-ops-engineer/

The above postings open on a revolving basis. If they're not open, just email us at [email protected] or [email protected], where we can answer questions and accept your application.

Feel free to reply on thread with any questions.

Login.gov | REMOTE or Washington, DC | Software Engineers, Site Reliability Engineers, Security Engineers | Full-Time | https://login.gov

Login.gov gives the public simple, secure access to multiple US government services through one verified account. We're working to fix online identity for US government services. The Login.gov team operates like a startup within the government, working in the open as a distributed, agile team. The core product is open source, hosted in modern cloud infrastructure, and built for scale. Tens of millions of people have Login.gov accounts, and we aim to be the preferred entrypoint for all government digital services. Our users include people accessing benefits, applying for government jobs, serving in the military, and collecting funds awarded through grant programs.

Find us on Github: https://github.com/18F/identity-idp

The Login.gov project began as a collaboration between 18F and the U.S. Digital Service (USDS). Today it's part of the Technology Transformation Services (TTS). You'll join other software engineers delivering better public services through modern technology.

* Ruby Software Engineer: https://join.tts.gsa.gov/join/application-engineer/

* Site Reliability Engineer: https://join.tts.gsa.gov/join/devops-engineer/

* Security Engineer: https://join.tts.gsa.gov/join/security-ops-engineer/

The above postings open on a revolving basis. If they're not open, just email us at [email protected] or [email protected], where we can answer questions and accept your application.

Feel free to reply on thread with any questions.

Login.gov | REMOTE or Washington, DC | Software Engineers, Site Reliability Engineers, Security Engineers | Full-Time | https://login.gov Login.gov gives the public simple, secure access to multiple US government services through one verified account. We're working to fix online identity for US government services.

The Login.gov team operates like a startup within the government, working in the open as a distributed, agile team. The core product is open source, hosted in modern cloud infrastructure, and built for scale. Tens of millions of people have Login.gov accounts, and we aim to be the preferred entrypoint for all government digital services. Our users include people accessing benefits, applying for government jobs, serving in the military, and collecting funds awarded through grant programs.

Find us on Github: https://github.com/18F/identity-idp

The Login.gov project began as a collaboration between 18F and the U.S. Digital Service (USDS). Today it's part of the Technology Transformation Services (TTS). You'll join other software engineers delivering better public services through modern technology.

* Ruby Software Engineer: https://join.tts.gsa.gov/join/application-engineer/

* Site Reliability Engineer: https://join.tts.gsa.gov/join/devops-engineer/

* Security Engineer: https://join.tts.gsa.gov/join/security-ops-engineer/

The above postings open on a revolving basis. If they're not open, just email us at [email protected] or [email protected], where we can answer questions and accept your application.

Feel free to reply on thread with any questions.

If there's not an obvious security contact at the agency, you can always report vulnerabilities to US-CERT, which has overall responsibility for connecting reporters to the right responders. https://www.us-cert.gov/

This links to the report form at https://www.kb.cert.org/vuls/govreport/

As with all vulnerability reporting, it's much more likely that someone will take action on your report if you can provide evidence or a reproducible proof of concept.

18F/TTS can sometimes direct reports to the right place, but it's really not their job to do so.

Login.gov | REMOTE or Washington, DC | Software Engineers, Site Reliability Engineers, Security Engineers | Full-Time | https://login.gov

Login.gov gives the public simple, secure access to multiple US government services through one verified account. We're working to fix online identity for US government services.

The Login.gov team operates like a startup within the government, working in the open as a distributed, agile team. The core product is open source, hosted in modern cloud infrastructure, and built for scale. Tens of millions of people have Login.gov accounts, and we aim to be the preferred entrypoint for all government digital services. Our users include people accessing benefits, applying for government jobs, serving in the military, and collecting funds awarded through grant programs.

Find us on Github: https://github.com/18F/identity-idp

The Login.gov project began as a collaboration between 18F and the U.S. Digital Service (USDS). Today it's part of the Technology Transformation Services (TTS). You'll join other software engineers delivering better public services through modern technology.

* Ruby Software Engineer: https://join.tts.gsa.gov/join/application-engineer/

* Site Reliability Engineer: https://join.tts.gsa.gov/join/devops-engineer/

* Security Engineer: https://join.tts.gsa.gov/join/security-ops-engineer/

The above postings open on a revolving basis. If they're not open, just email us at [email protected] or [email protected], where we can answer questions and accept your application.

Feel free to reply on thread with any questions.

Login.gov | REMOTE or Washington, DC | Software Engineers, Site Reliability Engineers, Security Engineers | Full-Time | https://login.gov

Login.gov gives the public simple, secure access to multiple US government services through one verified account. We're working to fix online identity for US government services.

The Login.gov team operates like a startup within the government, working in the open as a distributed, agile team. The core product is open source, hosted in modern cloud infrastructure, and built for scale. Tens of millions of people have Login.gov accounts, and we aim to be the preferred entrypoint for all government digital services. Our users include people accessing benefits, applying for government jobs, serving in the military, and collecting funds awarded through grant programs.

Find us on Github: https://github.com/18F/identity-idp

The Login.gov project began as a collaboration between 18F and the U.S. Digital Service (USDS). Today it's part of the Technology Transformation Services (TTS). You'll join other software engineers delivering better public services through modern technology.

* Ruby Software Engineer: https://join.tts.gsa.gov/join/application-engineer/

* Site Reliability Engineer: https://join.tts.gsa.gov/join/devops-engineer/

* Security Engineer: https://join.tts.gsa.gov/join/security-ops-engineer/

If the above postings aren't open when you want to apply, email us at [email protected] or [email protected].

Feel free to reply on thread with any questions.

This is a poor way to handle library upgrades that are guaranteed to break any existing compiled binaries.

Frustrating that my PR to create readline@7 was rejected. https://github.com/Homebrew/homebrew-core/pull/36782

I would at least like to see some mechanism to exclude a Formula from automatic gc of old versions besides brew pin. Libraries don't take up significant space, and they cause a world of hurt to delete out from under compiled binaries, so there is not a good argument for automatically deleting them.

The white "Access Denied" page is to help you empathize with Jony Ive, still trapped in a white room after all these years.

https://www.change.org/p/apple-free-jony-ive-from-his-white-...

It's interesting how your eye naturally groups the pentagons into the larger primitive unit, like the pinwheels of type 5.

Wolfram Alpha also has some things about tiling: http://www.wolframalpha.com/input/?i=pentagon+tiling http://www.wolframalpha.com/input/?i=pentagon+type+5+tiling

Enforcement of nameConstraints is inconsistent at best.

I experimented with name constraints a couple years ago for a private CA project, with the idea that I could restrict the private CA to issuing only names within a chosen subdomain.

I remember being able to enforce nameConstraints on the subjectAltName, but I was never able to get it to enforce anything on the subject Common Name. In theory new certificates should always have a critical subjectAltName extension, but this makes it worthless in practice.

It's also possible that my X.509 foo is not strong enough, or that I was testing with an older version of OpenSSL that doesn't implement it.

http://blog.codekills.net/2012/04/08/adventures-in-x509-the-...

ab

Recent submissions