We (Rizin) would love to improve QNX support of our FOSS reverse engineering and debugging framework. We already support[1][2][3][4] it, but can't reliably test. Would be awesome to have the QEMU image out of the box, just like Windows provides ready to use limited VMs for testing[5].
Unlike European supergrid there are not many news about this project. And given that last mention was in 2013 and completion date is set for 2020-2025, it looks abandoned.
> Man likes to think of himself as a rational animal. However, it is more true that man is a rationalizing animal, that he attempts to appear reasonable to himself and to others. Albert Camus even said that man is a creature who spends his entire life in an attempt
to convince himself that he is not absurd.
-Elliot Aronson, "The Rationalizing Animal"
Or to be less philisophical: the people with the money and power to say what's important are rarely the ones thinking long term, nor in an audience of other powerful, rich people thinking long term. US congress' median age is over 60: most aren't thinking about how to keep the Earth alive in 20-30 years. They won't be around to suffer the consequences.
I’ve seen this sentiment repeated over and over in this thread without a single explanation.
Please explain how NAT on IPv4, as used in practice, does not increase security vs connecting machines each directly to a publicly accessible Internet address?
I’m having a hard time understanding how this statement can possible be true.
That's bullshit.
"Security" is not a binary switch. NAT is a useful tool in your security toolbox when you want a more nuanced take than either "ban all ports" or "let every port flap open on the internets, #yolo".
Why is there a difference in captcha exposure between IPv4 and IPv6 then? Maybe there is no actual security, but the people deploying these captchas seem to think there is a need to deploy them for IPv6 users.
The Portal now loads for me on IPv6, which then blocks me from accessing certain PaaS resources because they only work with IPv4 rules in their firewalls.
Speaking of which, it grinds me gears that every Azure PaaS service implements firewall rules in a unique and special way. The syntax is different, the parameters are different, the capabilities are different, and the output logs are also incompatible just for extra fun.
Well, they provided something and it’s from a reputable publication. You can wait around for more people to chime in or you can dig in yourself until then.
Laypeople are much more likely to learn something useful and solid from a good podcast on a topic, run by someone (or with a guest) who has read the literature broadly and can distinguish solid papers from publish-or-perish drivel. Doing your own research, unless you dedicate an inordinate amount of time or energy to it, is very likely to lead you completely astray.
[1] https://neomutt.org/
reply