lox

17 ms·

121.
by lox 10y ago
Makes sense. I missed that section, much clearer now, thanks. Any plans to release more details on how the bastion hosts are configured? Seems like that would be the complex bit to get right.
122.
by lox 10y ago
To be clear they said they "could" use RevokedKeys. See my reply further down for my line of thinking.
123.
by lox 10y ago
I get that, but you need to update the revocation list on every single server. At which point you've just undone the benefit of not having to manage `authorized_keys` on each server.
124.
by lox 10y ago
Interesting, so I'm assuming this wouldn't work for staff that roam with laptops?
125.
by lox 10y ago
So staff that leave have 1 week of access to production systems?
126.
by lox 10y ago
How do they handle revocation? The problem I had with this approach in the past was no CRL support.
127.
by lox 10y ago
I could imagine drafts have much less diligent deletion policies vs sent emails. Auto-save mechanisms typically keep a long history of diffs, or whole versions.
128.
by lox 10y ago
Imagine a team of 20 developers sharing cloud infrastructure. Key additions and revocations ends up being time consuming.
129.
by lox 10y ago
Sometimes it's painful to realize how not economically rational people are.
130.
by lox 10y ago
Nope, funds were returned. Bank "made a business decision" to close account and decline any future accounts of mine with them.
131.
by lox 10y ago
Unless you are going to link to an actual definition, this is rude and worse, incorrect. The word "employ" is yours, not the OPs. Paying someone to work on your house doesn't violate personal use, much like paying a house cle
132.
by lox 10y ago
Agreed, we do this as well at some scale. The vast majority of application configuration falls into this category. The advantage of storing them in a git repo (we use a different git repo to the main codebase) is that you can re-use the sam
133.
by lox 10y ago
I'm not sure what your point is. Your initial comment seemed to indicate that you thought Github was increasing their pricing because they were struggling to pay for the underlying infrastructure, or that the per-customer cost was too
134.
by lox 10y ago
Pricing is a function of what people will pay for it, not what it costs to make. Consider Slack as a fine example.
135.
by lox 10y ago
This is not how pricing works.
136.
by lox 10y ago
https://developer.github.com/guides/managing-deploy-keys/
137.
by lox 10y ago
That's fine if you have a single repo, but CI normally needs to access lots of different repos. GitHub's documentation describes why you need machine users for anything but the most trivial deployment. https://developer
138.
by lox 10y ago
Pretty angry that Github have made this change with no mechanism for adding machine users without paying a per month charge. It seems like a key feature, which is currently horribly painful to manage and now expensive. How does everyone els
139.
by lox 10y ago
The issue is he'd have to be a cryptography "genius", so the fact that he can't provide a simple cryptographic proof speaks volumes.
140.
by lox 10y ago
I wrote a benchmark a while back: https://github.com/lox/s3-bench
141.
by lox 10y ago
This sounds like a really premature optimization to me. Let the DB do it's job unless you have an explain trace showing it's slow for your workload. Trying to do things like sequence columns adds complexity, when this is often han
142.
by lox 11y ago
I think the point is that people don't particularly care whether TE will be able to provide more stable updates, because they are fine with the current functionality at the current price. Perhaps in this case TE should have done a bett
143.
by lox 11y ago
https://www.schneier.com/crypto-gram/archives/1998/1215.html... http://thoughtcrime.org/blog/telegram-crypto-challenge/
144.
by lox 11y ago
Is it though? What's the point of a 1.0 release this far into a projects life? If it's utterly meaningless what's the point of versioning it at all?
145.
by lox 11y ago
Cfoo ( https://github.com/drrb/cfoo ) is great, it's simply a yaml-to-json converter with some syntactic sugar for cloudformation. Troposphere seemed like too heavy an approach.
146.
by lox 11y ago
As a counter point, we use Cloudformation extensively at 99designs and whilst it has some quirks, it's also been stable, reliable and incredibly beneficial for automating lots of our infrastructure.
147.
The misunderstood X-XSS-Protection(blog.innerht.ml)
4 points by lox 11y ago|0 comments
148.
by lox 11y ago
Only in America
149.
by lox 11y ago
Point in case?
150.
by lox 11y ago
Or just a troll :)

More ›