557 karma · joined February 13, 2010
This is probably overkill for most use-cases (particular for a consumer-level VPN), but it's a nifty addition if you fear your WireGuard keys may be stolen at some point.
Now that's pretty interesting -- being able to mod your car via APKs!
You should form an LLC in the state where you live. Here's a nice guide for how to do this in California:
Delaware in particular can be more pricey than most states, since their infrastructure is oriented towards enabling third-party services (DelawareInc, IncNow, etc) instead of interacting directly with your business. Prepare to wait weeks for them to mail you copies of your documents unless you pay a third-party service to expedite.
The advantage of forming in Delaware is that there's lots and lots of settled business case law; but that's generally not relevant to a sole-proprietor LLC. (It is relevant, however, if you're forming a company with the aim of raising venture capital -- in which case you really want a Delaware C-Corp, not an LLC.)
But three things mentioned in their report do give me some confidence about the way CircleCI has engineered their internal systems:
1. They use SSO with 2FA ("an unauthorized third party leveraged malware deployed to a CircleCI engineer's laptop in order to steal a valid, 2FA-backed SSO session")
2. They maintain reasonably good audit logging (they could identify that "the third party extracted encryption keys from a running process, enabling them to potentially access the encrypted data" which had been exfiltrated)
3. They can rebuild everything from scratch ("we rotated all potentially exposed production hosts to ensure clean production machines")
A lot of companies pay lip service to best practices like these, but don't actually implement them thoroughly (or at all). The fact that CircleCI could rely on them under attack makes me think they're doing a better job than 90% of the SaaS companies out there.
1. You may be using an older version of openssl, but with modern versions, add the `-pbkdf2` option for much saner key derivation.
2. With modern versions of openssl, the `-salt` option is on by default, so you don't need to specify it explicitly (and you almost certainly want this option on, versus not using a salt or generating one yourself).
3. Since no AEAD modes are available with this tool, CTR mode (the `-aes-256-ctr` option) might be the best mode to use with AES (see https://security.stackexchange.com/questions/27776/block-cha...).
4. Alternatively, you might prefer to use ChaCha20 (the `-chacha20` option) over AES (see https://crypto.stackexchange.com/questions/34455/whats-the-a...).
So I would suggest this for the encryption command (instead of `openssl enc -aes-256-cbc -salt -a`):
> openssl enc -chacha20 -pbkdf2 -a
Also, instead of using openssl, you might prefer to use `age`, as it uses modern crypto best practices by default (see https://age-encryption.org/). With it, you could substitute this encryption command for the above:
> age -p -a
> "This is a cartoon super-villain of an app," said Gennie Gebhart, the Electronic Frontier Foundation’s advocacy director. "The biggest red flag is the number of permissions required, which is unnecessary for the operation of the app and suggests they are trying to surveil attendees."
The dumbest, silliest, and rudest comments and commenters get promoted on Twitter (and Facebook etc), because that gets the most clicks. Get rid of all that manufactured promotion, and what's left is a quieter space where users can self-organize their own communities -- more like a chill party or friendly conference hallway than a staged political rally.
You might also want to look into the burgeoning low-code/no-code space, if you need something a little more complicated. If it turns out you need to do more serious programming, however, that's when it's probably time to look for a technical co-founder.
Also, because life is short and your savings aren't infinite, set some metrics (X many users, Y much revenue, Z much funding, etc) to meet under some time horizon (3 months, a year, etc), and when that time point arrives, if you're not close to your goals, fold the company and try something new.
You'd be essentially Employee #1 with a fancier title (and more sway if they take the C in your title seriously). If the amount of equity is important to you, you should go start your own startup from scratch. But if you like and trust the founders, and are excited about what you would be doing, then the equity is just a bonus for being a key player in getting the company successfully to its next stage.
This is what you'd typically do to point a custom domain (eg example.dev) that you've registered through one DNS-hosting company to a website that you've set up with a different web-hosting company:
https://docs.netlify.com/domains-https/custom-domains/config...
- Conceptual Overviews: High-level "explanations" (broader instead of deeper).
- Examples (and case studies): "How-to guides" that focus on more narrowly-specific use cases instead of more general or common ones.
- FAQs: "Reference" -- what readers want from FAQs are short concise answers, ideally with links to further details.
- Troubleshooting: "How-to guides" that focus on fixing common problems.
- Best practices: Opinionated "explanations" that focus just on best practices -- the best "best practices" guides explain why, not just what.
> The CISA and NIST Directors are working on developing technical standards for quantum-resistant cryptography for each of their respective jurisdictions, with the first set to be made publicly available by 2024.
So nothing new to be alarmed about, just doing appropriate planning for the future of cryptography over the course of the next few decades.
1. Establish universal "soft deletes" across all systems.
2. Better DR for multi-site, multi-product incidents.
3. Fix their incident-management process for large-scale incidents.
4. Fix their incident communications.
Regarding #4 in particular:
"Rather than wait until we had a full picture, we should have been transparent about what we did know and what we didn't know. Providing general restoration estimates (even if directional) and being clear about when we expected to have a more complete picture would have allowed our customers to better plan around the incident....
[In the future], we will acknowledge incidents early, through multiple channels. We will release public communications on incidents within hours. To better reach impacted customers, we will improve the backup of key contacts and retrofit support tooling to enable customers... [to make emergency] contact with our technical support team."
* The Pragmatic Programmer, by Dave Thomas & Andy Hunt
* Scalability Rules, by Marty Abbott & Michael Fisher
* Release It!, by Michael Nygard
So use the tools and platforms that you already know, that you can hire for, and that will allow you to try out changes rapidly. Do everything you can to keep things as simple as possible for as long as you can -- the more architectural pieces you add now, the more you will have to change later.