New third party firmware (Not HP'PRIME TEAM)

[matthiaspaul]

(12-30-2015 03:08 PM)DrD Wrote:  To clarify, it's not about "new software development," you missed that part. It's about non-descriptive third party software (in this case). Users may be able to read something about it, but third party firmware is unrestricted in consequence, ("if it blows up prematurely...").

Actually, proprietary firmware is unrestricted in consequences as well - just think about the shameful large number of severe bugs in the Prime.

And in the case of closed-source software, you even have to blindly trust in the competence and integrity of the developers. The list of proprietary software which should better not be trusted if you take care about security and privacy is virtually endless, and this even includes many products from some of the largest software companies.

Open-source software isn't free of bugs, of course, but you don't need to trust anyone, if you don't want to. Instead, you can inspect the source code yourself and even build your own binaries if you don't trust others doing this for you. If you find bugs or shortcomings, you can fix them yourself, instead of relying on some product manager's business plan, who might not be interested into fixing your problems for commercial reasons in the first place or might abandon the product anytime later, even if you depend on it (see f.e. the still quite long list of remaining unresolved bugs in the now discontinued HP 50g firmware - if this would be open-source software, you could bet on that none of these bugs would remain at this time). So, using open-source software you are, at least potentially, much more on the safe side then using closed-source proprietary software.

Regarding documentation. There's good and bad documentation. This does not depend on if the software is proprietary or not. In fact, some of the best software documentation I have ever seen is for "alternative" close-source software products and open-source software.

Quote:

(12-30-2015 01:46 PM)Claudio L. Continuing, also ' Wrote:  Creating a new firmware doesn't require "devious methods", just reading some manuals and basic information about the physical device.

A suite of tools are employed to crack existing software, etc. These 'devices' are the "devious," [devised], means referred to;

You don't need to crack existing software to upload a new firmware onto a device such as the Prime, you just need to read the processor manuals. The existing software gets replaced by a new one. Nothing devious here.

Quote:The Prime, as far as I know, is not open source.

It isn't.

Quote:I know that legalities are the first victims to fall,

There's nothing illegal in reflashing a device with a different firmware. You'll obviously loose the vendor's warranty, but that's it.

Quote:Suitably motivated, anyone can hack the device, but few can you do that with the blessing of full hp support.

We are lucky to have a few HP developers in this forum who help out with some user-level support in their free time in exchange for learning about problems with their products first hand and getting feedback about how to possibly improve their products. It's beneficial for both parties.

Official HP support was great decades ago. Today, it is for the most part non-existant, unfortunately - most of those hotliners are completely clueless about their products.

Greetings,

Matthias