I would guess that could show some kind of open() and "not found" or other syscalls on file descriptors like stderr just before crashing and that could be good leads or where into look next.
283 karma · joined November 16, 2011
https://twitter.com/RobOlmos
https://www.linkedin.com/in/robolmos
I would guess that could show some kind of open() and "not found" or other syscalls on file descriptors like stderr just before crashing and that could be good leads or where into look next.
There's also a WebAuthn extension in the works to at least make it easier to maintain a backup key by not having to pull it out of the safe every time you register MFA with a new service:
https://www.yubico.com/blog/yubico-proposes-webauthn-protoco...
https://web.dev/fetch-metadata/#step-5:-reject-all-other-req...
Back in the day a very popular registrar that included DNS service would have random issues with the size of DNS response when it switched over to TCP, returning servfail instead of answer.
I'm guessing it was a load balanced cluster and some of the servers were broken. We reported the issue a few times but never heard back, as expected.
Whether they're helpful in all server-side error situations I'm not sure.
1: https://stripe.com/docs/idempotency#sending-idempotency-keys
2: https://stripe.com/docs/error-handling#the-stripe-should-ret...
Are there other blockchains that are similar? Is there a strict subset and prover for Solidity or other languages? Or things like proven smart contract kernels that can be built on top of? Eg, OpenZeppelin Contracts, but with provers rather than only audits.
So, can't put a CNAME on the apex, which probably also has MX records. I think in some cases like Exchange, if it sees a CNAME, it doesn't bother with looking at the MX.
Back in the day "CNAME flattening" or aliases (RFC draft draft-ietf-dnsop-aname) wasn't a common thing, so only real way was to redirect the domain apex to www, and then use a CNAME on the www. You'd probably need a separate service/servers to handle that redirect (at least DNS round robin would work in this case). So yea extra complexity in that case, due to the requirements. Or, give them DNS authority (eg, AWS Route 53).
Then there's the whole era of TV/radio commercials telling people "www dot <name>" that a lot of people type it anyways. You can redirect www to apex, which some sites do for a "clean brand" but now browsers are dropping the www in the UI anyways.
I've also run into plenty situations where www worked but apex didn't. Relatedly, it's a little surprising that browsers didn't default to assuming typing the apex in the browser it would try www first. And recently, now we're getting SVCB and HTTPS DNS RRs along with A/AAAA (and maybe ANAME). Indeed lots of complexity.
Auto-refreshing the popular records in the background before the TTL expires to help smooth over any temporary issues?
Other big name DNS providers have ALIAS type records. I imagine according to the SLA, AWS Route 53 is still "available", even if it can't resolve a "target address record" (as the ANAME draft calls them) but Route 53 is still able to respond.
I don't want to beat a dead horse at this point, but that's basically a planned blackout. It'd be similar to a power company cutting off a residence's power for a couple hours to remind them to pay their overdue bill. I can't see that being correctly called a brownout.
Regarding the offensiveness, I was hinting at GitHub's prior remarks for racial sensitivity: https://news.ycombinator.com/item?id=23500093 -- among the many other projects that have actively changed black/white to block/allow and other variations.
CloudLinux also announced a free alternative: https://blog.cloudlinux.com/announcing-open-sourced-communit...
Some additional helpful info in this answer: https://serverfault.com/a/714070/53160
That's the RFC3597 encoded form, probably because it's an unknown RR type. Taking a quick stab at decoding some of it according to "draft-ietf-dnsop-svcb-https-01":
\# 76 length; 0001 priority; 00 full registered name, null, "."; 0001 alpn key type; 0015 alpn value length; 05 alpn-id length; 68332D3239 alpn-id: h3-29; 05 alpn-id length; 68332D3238 alpn-id: h3-28; 05 alpn-id length; 68332D3237 alpn-id: h3-27; 02 alpn-id length; 6832 alpn-id: h2;
I'm not sure if a Yubikey's simplest mode as a HID device can read the device's wall clock it's attached to without additional drivers?
and Google being prepared for smart devices like toasters that have enough resources to run GTM code with an ad blocker.
I tried changing the "Site access" setting to "On click" -- but then the extension started acting funny or not working in some cases.
Chrome has added a more limited "activeTab" permission[2], but even that might be too much since it grants control to the tab and continues to allow permission on the same origin.
Like the GP said, even if the extension developer isn't trying to exfiltrate data, they should do more to protect users from a compromise of their extension, and browsers should give them the models to do so.
IMO, good security models can be a foundation forward to better overall security compared to desktop apps since it seems that browsers are becoming an OS of their own.
1: https://help.getpocket.com/article/912-what-permissions-does...
Ie., you have a RUM sample rate less than 100%, so some errors aren't recorded in RUM Errors? Will that be the same situation for "Error Tracking"?
Curious to see what this pricing is.. eg., any client-side errors get auto-included as a RUM session? There's a good amount of bogus browser errors due to incomplete or oddly sandboxed javascript environments.
I'm on the fence though if I would want a separate region for this with various random failures. I think I'd be more interested in being able to inject faults/latencies/degradation in existing regions, and when I want them to happen for more control and ability to verify any fixes.
Would be interesting to see how they price it as well. High per-API cost depending on the service being affected, combined with a duration. Eg, make these EBS volumes 50% slower for the next 5min.
Then after or in tandem with the API pieces, release their own hosted Chaos Monkey type service.