HN Simulatornew | past | comments | lists | submit | 8organicbits's commentslogin

Password reuse is the problem. The password hash is stolen from some other site and brute forced offline.

Same issue with key reuse. Unless you have a policy to rotate them and verify which host they login from, someone's unencrypted hard drive from 5 years ago is more likely to have a key than password.

> someone's unencrypted hard drive from 5 years ago is more likely to have a key than password.

Even 5+ years ago, hardware-backed SSH keys were a thing (Yubikey). The only difference today is that its 100% easier to do keys properly because of the widespread commoditisation of secure enclaves in desktops and smartphones to support FIDO, its basically free of charge now because you're not obliged to buy a Yubikey.


I feel like they should release manual update instructions since the update mechanism is vulnerable. Although I see my systems already updated via unattended upgrades.

edit: On lobste.rs I see a recommendation for `apt download`: https://lobste.rs/s/h7bvma/man_middle_arbitrary_code_executi...


CVE says you need a non zero retries, so you can use Acquire::Retries=0 to avoid the issue completely (unless your packages were modified already of course).

How often do you see self-signed certificates that are valid due to DNSSEC/DANE configuration versus certificates were issued by a trusted CA? When I checked two years ago I found that 99.3% of the top 1,000 domains supported STARTTLS and 94.1% used a TLS certificate issued by a CA. I suspect the numbers keep improving, but I don't think we're quite at 100% yet.


This is a good overview of email encryption, but it doesn't cover what Fastmail actually supports which I think makes this misleading.

Fastmail does not enforce MTA-STS for outbound messages. I just checked here (https://email-security-scans.org/view/jktrld5e73b2dyxz0h1swu...). You can see how your email provider compares at https://email-security-scans.org.

Fastmail does support MTA-STS for inbound messages... sort of. For inbound MTA-STS the email provider needs to use a TLS certificate issued by a trusted certificate authority, which Fastmail does. Additionally, the domain name in the "to address" needs to enable MTA-STS using some DNS records. Fastmail does not provide the documentation for setting this up, although they have decent adoption by folks who figured it out on their own. I'm seeing about 0.2% of domains using Fastmail enforce MTA-STS inbound:

    SELECT mta_sts_mode, COUNT(*) AS "count"
    FROM read_parquet('dns-analytics-2026-q3-*.parquet')
    WHERE exchange_suffix = 'messagingengine.com'
    GROUP BY mta_sts_mode
    ORDER BY count DESC;
    ---
    mta_sts_mode  count
    -             174,877
    enforce       354
    testing       313
    none          11
This is about the same as Protonmail (~0.2%), but higher than Outlook (~0.1%) and Google (<0.1%). I suppose this reflects Fastmail's popularity among technically minded folks.

I'd like to see Fastmail improve this by clearly documenting MTA-STS support, setup instructions, and validate MTA-STS in their custom domain dashboard. It looks like they may be adding MTA-STS policy hosting, which is a really promising sign, but I don't see this documented yet so this is probably being tested internally.

    $ curl -k --resolve mta-sts.example.com:443:103.168.172.47 https://mta-sts.example.com/.well-known/mta-sts.txt
    version: STSv1
    mode: testing
    mx: *.messagingengine.com
    max_age: 86400
With that said, I've been extremely happy with Fastmail for several years now and recommend it.


I think this is a clever happy path solution, but it isn't very defensive against problems. If the cloud cron doesn't fire on time or the consumer fails then the queue won't be drained in time. That will cause the events to be batched in the wrong hour.

I don't see how you are building the batches, but there's a lot of complexity around batch sizes, acknowledging that the messages were consumed, etc. Having a single dataset.json.gz per hour feels like a hint this isn't done safely. I'd double check that carefully to avoid losing data.

One tip about compression, I've been really pleased with zstd compression of json/jsonl data.


This looks clever. I've seen PPT to web tools before (https://sparkslides.com/publish/, https://slidehtml5.com/), but I think the slide synchronization idea is new. I can't evaluate more than that as I don't use these.

In the past I have liked marp (https://marp.app/) for technical slides as you write in markdown, can use version control, etc. Powerpoint always felt odd as a developer.

To share public slides I've published to GitHub pages (https://github.com/robalexdev/marp-to-pages). I've seen professors use it for all their slides. But that doesn't synchronize slides, last I checked.


Reveal.js with the multiplex plugin [0] does that. I write my presentation in Quarto [1] and render them to reveal.

0: https://revealjs.com/multiplex/

1: https://quarto.org/docs/presentations/revealjs/


I've been working on a similar project that turns Typescript into an actual pptx deck you can generate or render in the browser. It is more complex than markdown (the slides are code), but works nicely for version control and having an AI agent generate a deck with (almost) all PowerPoint features (https://github.com/shbernal/pptx-ts)


I've used FreeDNS on occasion for test domain names, one-off experiments, and similar. I'm very appreciative this exists, but there are some pain points that similar services handle better.

The domains are missing from the public suffix list. This impacts how cookies are handled by the domain names, with concerns the browser will allow software to set the cookie on the shared domain name instead of the subdomain. This can be a security problem. Getting added to the PSL may not happen: https://github.com/publicsuffix/list/pull/79

It can be difficult to get a free HTTPS certificate for your subdomain. Let's Encrypt applies per-domain name rate limits and these domain names see lots of issuance requests. There's a process to lift those limits, but last I checked FreeDNS didn't use it. You can still, of course, pay for a certificate.

There's tons of abuse on free domains so you may find that your domain is blocked on various lists.

Here are some compelling alternatives I use now, which manage these issues better:

- https://messwithdns.net/ - Exceptionally well-made DNS console for learning DNS

- https://open-domains.com/ - Uses Cloudflare, great Discord group

- Even more: https://free.hrsn.dev/#/?id=domains


The entire publicsuffix thing is such a mess. The fact that project even exists is ridiculous. Why can this not be a dns setting?


They should have never allowed cross subdomain access for cookies. Every subdomain should be treated as completely unrelated to all other subdomains.


sigh

See, before the cloud, you used to deploy your code to actual physical servers. If your site became really popular you needed more than one server to run it.

Before commercial and open source load balancers became a thing we literally used HTTP redirects to distribute load. You might visit www.example.com and get redirected to www13.example.com, which was an actual box in a datacenter.

I don't think the internet would exist today if websites just randomly fell over once the number of simultaneous users exceeded the capacity of a single server.


When I was at yahoo, we certainly had load balancers, but we didn't have super fancy load balancers that could separate traffic out by path, so each 'property' would use a different hostname (i worked on travel.yahoo.com, which is dead these many years), but we all shared a login cookie (and some other cookies).

We'd have certainly adapted if we couldn't share cookies, but it would have been a lot messier.


Why? That looks like a mess. Proxies existed before http, so why not just proxy traffic between your various physical servers to manage load? It’s literally a poor man’s load balancer. It how Travelocity worked way back in the day.


Then use an http header like we do with CORS or something, which lets a domain set a cookie for another domain that opts in. Or, you can just include the necessary cookie info in the redirect.


Couldn't you just ghetto load balance by using internal DNS to round robin to a spread of servers with different internal IP ?


DNS caching and thus the load distribution is outside the control of the entity running the servers. You assume you get roughly same traffic on each of the published IP addresses, you even think you can advertise some address twice so that it gets twice the load vs other severs (if you just set up a server capable of serving twice the traffic), but the reality is one of these IP addresses might be used for 90% of the requests (as an example) due to caching and bad luck.

So no, you cannot reliably control load balancing using one domain name pointing to multiple IP addresses. (IP anycast is better suited, but much harder to implement)


One of the complications that gets discussed is that there are way too many use cases with different requirements on what it means for domains to be related. The cookie problem is something browsers need to solve, so its perhaps reasonable that Mozilla (and volunteers) manage a list that focuses on that user case. But that's poorly suited for other use cases.

There's a lot of people thinking about this though. One somewhat related example is https://datatracker.ietf.org/doc/draft-manelidis-dnsop-domai..., which has a double-opt-in DNS TXT record mechanism. That draft and forthcoming discussions on the mailing list are a good place to understand the complexities here.


If, for example, you could trick a client into thinking "com" was not a public suffix, then from malicious.com you could set cookies on paypal.com

DNSSEC is not widely deployed, and so we cannot rely on the authenticity of DNS.

Maybe if we had DNSSEC, then we could rely on it for publicsuffix. Maybe lots of others things could be more easily solved if we had that too.

DNSSEC automation is coming, e.g. https://www.rfc-editor.org/info/rfc10026/. It might never become mainstream, but don't let anyone tell you that we couldn't benefit from having DNS authenticity!


because, like everything, bad guys would abuse it, causing a list of "bad publicsuffix" to exist, which is basically the same thing.


Could we just publish (and cache!) TXT records at the appropriate-level domains? E.g.:

  host -t TXT github.io.
  etld_depth=2


badguy.com would set the same flag, allowing a.badguy.com, b.badguy.com, c.badguy.com to count as fully independent sites


(Vouched so I could reply.)

Why would that be a bad thing? What happens under badguy.com is badguy.com's business, is it not?

Is it any different than setting cookie scoping rules?


The cookie use case is just one use case. Another PSL use case is helping browsers decide what part of the FQDN is most important for the user to notice. On firefox I see "ycombinator.com" in bold, with normal font weight on the news subdomain. On smaller screens the URL bar isn't left aligned, it adjusts the view to prioritize showing the relevant domain name. You don't want an attacker to control how the URL is displayed in that security context.


It’s also strongly used by chrome and similar browsers so malware at randomuserdomain.geocities.com doesn’t block the entire root domain.


In some situations it is most convenient/practical to have your router do dynamic DNS updates and depending on your router the options may be limited giving you no "great" options.

Regarding your valid concerns about the PSL, as long as you have a domain already, you can just make a CNAME record to a free dynamic DNS provider's sub-domain record, I've done this for years with a No-IP ddns.net record. I don't especially recommend No-IP as the 30 day verification is a bit annoying, but at < 1 minute of work per month, it's tolerable for a free service and $2.50 a month is an order of magnitude more than what I feel a single dynamic DNS record is worth.

Since I moved to having a pfSense box at home, I'm using Cloudflare for dynamic DNS, no extra fee and works perfectly, but like I said above, probably not available on typical home routers without a regular machine behind the router having to poll your IP to detect needed updates of a dynamic DNS record.

As I was on Namecheap, I was initially going to use their dynamic DNS option, but it turns out it's behind a higher fee to enable full API access to administering your domain, totally stupid, but with their having been bought out by the PE entity I wouldn't want to stay with them anyway.


> Let's Encrypt applies per-domain name rate limits and these domain names see lots of issuance requests. There's a process to lift those limits.

I'm familiar with the process to lift those limits, and Let's Encrypt has been amenable to bumping the certs as high as 250,000 but balked at 500,000, saying, "This is too large for us to support"

(I run a DNS service nip.io / sslip.io, and lots of my users request certs, so I'm always bumping into the limits)


I remember seeing a request to add nip.io to the PSL (they don't approve requests where the subdomains are IP addresses). What do you think the future of these sorts of services are now that Let's Encrypt offers free IP certificates?


I hope IP-based certificates will ease the pressure on nip.io/sslip.io.

I also hope I get fewer takedown requests. I currently get ~25 takedown requests every week (phishing, copyrighted material, illegal drug sales, unauthorized mirrors, command & control servers).


This is usefull, many thanks! Im building Keenrig, a self-shoting opensource app that gives users subdomains for their app, and your comment made me take another look at this. because some cookie issue . I'm moving user apps off my main domain (keenrig.com) onto a separate one - keenrig.app. the main reason is isolation: an app on a user subdomain shouldn't be able to set cookies for my console, or for other user'apps. many thanks


Doesn't Hurricane Electric do FreeDNS ? Haven't tested it but I assume with all their peering agreements they have decent latency


True. To get a free HTTPS certificate is a really difficult challenge, I think :)


Hey author here, thanks for reading the post. I haven't seen UUIDv5 used very often but I'll have to think about the idempotency angle more.

One thing that concerns me is that UUIDv5 is based on SHA1, which is an insecure hashing algorithm. I generated a pair of colliding UUIDv5s in an earlier post in this series (https://alexsci.com/blog/uuid-oops/#insecure-hash-functions). So I don't think you can use UUIDv5 for security critical functions.


Interesting! That said, these examples appear to be crafted in a special way to cause the collision. In a practical scenario with normal usage, I suspect it would be essentially impossible. Sure, it can be a problem in some niche scenarios with a determined attacker but a collision would just mean that the user is not able to create the resource (the system would falsely indicate that the resource already exists); but that's not too bad. At worst, it would reveal the existence of a resource with a specific UUID, but could the attacker have achieved the collision if they didn't know the target UUID already? It doesn't seem like a viable attack given how little information it gives you.


Correct, this is a very specific attack where an attacker can generate UUIDv5 collisions but cannot force a collision of a chosen UUID. If your usage doesn't serve any security functions then its fine to use an insecure hash function.

One thing I find interesting is that we seem to be at the end of the road for secure hash-based UUIDs. SHA-1 was already truncated (I.E. weakened) from 160 bits to 122 bits to fit the UUID width. To fit a SHA-256 hash you'd need to throw away a majority of the bits!


One concern about accuracy of the diagrams. In the example, there is a transition back to the session service labelled "wait for release" after the "no" decision. I'm not seeing that in the shown diff.

Looking at the code the "no" seems to relate to the context expiring, so you wouldn't want to wait more if the context already expired, you'd want to stop. Is there a reason that label exists?

I'm pretty wary of LLM development tools hallucinating and wasting my time, is that whats happening in the lease broker example?


Hey! oops, that gif is a notional one we were using for design, and we forgot to update it.

Real diagrams are all linked to code, so hallucinations don’t really happen in practice (hallucinated architecture really bothers me too!)

Will update shortly with an actual gif of the app. Sorry about that!


update: fixed - grabbed an actual whiteboard session that I had previously set up. thanks again!


The Kanopy model is fascinating. Library members get free views but there are limits as the library has to pay for those views. Our county library system has a Kanopy subscription at each library and county residents are eligible to become members at every location. Kanopy supports adding multiple library cards, so you can boost your limit.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: