I have no interest in furthering this conversation.

I don’t subscribe to your personal purity tests or agree with the logic on that one. The resources involved can be minimal, and I don’t really believe you have a ton of exposure to software engineering if you think all of the prototype code will need cleaned up or be entirely understood, especially with devices like these. There are significant amounts of binary blobs and drivers filled with post compiled obfuscated closed source code that nobody maintains or understands even in current Nura distributions, it’s a design of ip protections popular hardware manufacturers use and nothing guarantees the quality or maintainability of that code. Just because you don’t like or know how to use a tool does not invalidate it, and there’s no reason for you to apply genuine concerns to a tools entire existence or output.

Except it doesn’t bring it to all old phones, ai can massively help resolve this.

So is manufacturing new electronics. You don’t get a perfect solution, and frankly, local ai already exists that’s good enough for this type of prototyping. I’ve read through their reasoning and while I can sympathize, I do not agree with it. It’s not realistic or accomplishing their goals imo, but I maintain that’s the beauty of open source. Fork it. Move on. Thank them for their contribution.

The reasons stated are not immediate granted fact, nor are they all logical. Again, fork it and move on. Nura can have whatever policy they’d like, but it doesn’t make sense not to use a tool, that it should be obvious by now can accomplish the prototyping work of entire engineering teams. In a good enough fashion to create software for revitalizing what would otherwise be ewaste. To me that doesn’t sit well with their goals, at least as applied to this reality. You can have whatever opinion on it you’d like, I know there’s a cult of anti ai on lemmy and in open source software, and I do sympathize with some of their viewpoints and the legitimate concerns.

What a genuinely antithetical stance to take on a project meant to keep otherwise dying hardware alive, but that’s the beauty of open source. You don’t have to give a damn about upstream, just fork and rebase into your own little niche and move on.

🤔🤔🤔🤔🤔

https://arstechnica.com/information-technology/2022/02/after-lying-low-ssh-botnet-mushrooms-and-is-harder-than-ever-to-take-down/

Are we living in the same universe? In mine software doesn’t get patched all the time, in fact it’s usually a lack of patches that lead to any significant system compromise… Which happens time and time again. Also you’re on a thread that is advising hobbiests on how to configure and maintain their personal server, not the engineering meeting for a fortune 500. Yes, you can make ssh very secure. Yes, it’s very secure even by default. In the same regard, new vulnerabilities/exploits will be found, and it remains best practice not to expose ssh to raw internet unless absolutely necessary and with the considerations required to mitigate risk. Ssh isn’t even implemented identically on every device, so you literally cannot talk about it like you are. Idk why you’re arguing against the industry standard for best practices decided by people who have far more experience and engineering time than you or I.

I linked a relevant vulnerability, but even ignoring that, pragmatically, you feel they’d be targeting specific targets instead of just what they currently do? (That, by the way, is automating the compromise of vulnerable clients in mass scale to power botnets). Any service you open on your device to the internet is inherently risky. Ssh best practices are, and have been since the early days, not to expose it to the internet directly.

Doesn’t take that to leverage an unknown vulnerability in ssh like:

https://blog.qualys.com/vulnerabilities-threat-research/2024/07/01/regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh-server

That’s why it’s common best practice to never expose ssh to raw internet if you can help it; but yes it’s not the most risky thing ever either.