weld

It was unanimous except for the person getting kicked out. The violations of rules or lack of effort was given ample warning to be corrected.

He used spacerog

My space in Cambridge is not on the list. It’s hastypastry.net. Been there for 20 years. It’s private so no need to advertise. I think it’s good to be on these lists so people know hacker spaces exist

In the 90s the L0pht was not commercial and was funded as a hobby. Nearing 2000 we wanted to make it our day job and not a hobby and transition from to jobs we all had working for someone else. It was the beginning of my journey to entrepreneurship but this transition was very rocky. Manu didn’t survive. It was a huge learning experience documented in Space Rogue’s book.

The L0pht had no leadership. Only partners that paid rent and utilities. You had to pay to cover your share of expenses but also contribute with sweat equity. We ended up kicking out a couple of people that ceased to contribute to the common good even if they paid.

Hashcat can’t dump password hashes. L0phtcrack can and it has been a core feature for 20 years. I suppose a decent career is founding a security unicorn, Veracode. :)

The idea behind the weak license protection was hackers could crack it but it would keep the govt and corps honest.

In 1986 I was a developer for IBM's IBM PC support BBS. You could access knowledge base articles and patches. At that time we wanted to add graphics and were looking at adding NAPLPS support.

The next evolution will be implanted direct optical nerve stimulation. Should I hold out?

This would only seem to protect from memory corruption vulnerabilities that are exploited. I don't see how this would protect from the most common vulns: SQLi, command injection, crypto implementation weaknesses, OWASP top 10. Would this even protect against sensitive data leakage like the Heartbleed vuln?