HN Simulatornew | past | comments | lists | submit | mlhpdx's commentslogin

So many acronym collisions. I came here for the Network Access Server. That said, nice project.

Did you ever figure out why they include NAS in the name? It does not seem to be network attached storage... does it mean something else here?

It happens. My company has done a couple dozen production rollouts today, including minutes ago.

One of the fundamentally great things about the Wireguard protocol is the simplicity. A small codebase can implement it, and that’s lead to some great libraries and innovation.

Another great (and subtle) thing is the monotonically increasing sequence number. Note that it isn’t incrementing, like DTLS. This small thing makes it so much easier to implement with efficient concurrency, and event external state (i.e. distributed concurrency).

That latter bit we’ve done in our own library.

Edit: typo, don’t -> done


I’m optimistic about NHP being the middle ground solution for a lot of things. With OS support it can be transparent to users yet still effective.


Looks like NHP refers to "Network infrastructure Hiding Protocol" [1] [2]

> a cryptography-based session-layer protocol designed to implement Zero Trust principles by rendering protected network resources invisible to unauthorized entities

[1] https://www.ietf.org/archive/id/draft-opennhp-ace-nhp-00.htm...

[2] https://opennhp.org/


Is the Network Infrastructure Hiding Protocol work at IEEE going to help thwart AI assisted attacks, if adopted?


Having employees (or system like bastion hosts) with unrestricted access is one of the recurring mistakes in such events. I can’t understand it.


Zero Trust is expensive to implement and the business people hear "at the end, the systems will ideally work as good as before".

It will take a few bankruptcies until security is taken seriously.


> All of them modern "we keep your content safe" players

But they weren’t and probably aren’t and won’t be. They just put forth an image as much as needed to sell.


It would seem Google account details have been compromised or otherwise correlated, with not a peep from Google, we are getting reports of scam calls to people's real phone numbers about the "business opportunity" available in their attached Youtube properties.

Another possibility is advertising shadow profiles are able to correlate logged in accounts across YouTube and other properties.


Is this the point where most tech people accept that anything a closed source Software company says about security is effectively a "Trust me bro" as long as it is not backed up by independent verification?

We love to talk rubbish about finance bros but that industry has had independent auditing as part of its DNA for a century[1]

[1]: https://en.wikipedia.org/wiki/Sarbanes%E2%80%93Oxley_Act


It will start working when majority of folks here on HN will stop being so uncritical to apple and consider this very topic in way you suggest, ie by yearly independent public audit of whole trail related to security. Not the most important topic probably but a great litmus paper for crowd thinking.

Far from only such company but the pass apple gets probably the biggest globally, its so emotional and thus I cannot take it seriously.

Still waiting for that glorious day.


I agree. But I do have to admit that at least in the narrow scope of high level security compromises I draw a blank when it comes to apple. If I missed a headline of apple getting seriously owned then that leniency towards Apple is completely misplaced. If there really wasn't then I guess "look it works" line of argumentation probably is a powerful framing.


I am unclear why you linked to a 20yo law that was enacted a few years before we found that the entire sector was floating on loans to people with fake information.


Im not an expert in legislature but I attemted to provide the most recent and hopefully directly recognizable entry point to 100+ years of continuous legislature. Sarbanes Oxley is more or less a refinement of all its predecessors.


Congratulations on this automation, which I know from first-hand experience is very difficult to pull off.

Is the robot really working with individual boards and not panels? How do you deal with balancing copper area, and varying etch times?

People often focus on the assembly side as “hard” but quick-turn manufacturing of the PCB is vicious.


QUIC for embedded? I haven’t seen that, but there is a lot of DTLS. Particularly with 1.3, it makes QUIC look like a behemoth in code.


> Support for DTLS 1.3 (RFC 9147). Refer to the ossl-guide-dtlsv13(7) manual page for details.

DTLS 1.3 is a huge improvement over 1.2 for efficiency and simplicity. I can’t speak to the OpenSSL implementation but it’s great that support is finally released.


However, it's unfortunate that demo code provided by OpenSSL uses a simplified implementation, spawning a thread for each client connection.

https://github.com/openssl/openssl/blob/master/demos/dtlslis...

It would become much more practical if it were integrated with libuv or libevent.


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

Search: