• 0 Posts
  • 21 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle
rss

  • I think multiple people already have access to the databases that store the data the device sends. I don’t really care whether they get the data from the device itself or from the database.

    Similarly, I think multiple people have the ability to make changes to the firmware build and the systems that distribute it. So those people already have the potential ability to gain access to the device.

    One person or multiple people having unauthorised access are both unacceptable. I’m saying that the users have to trust the companies ability to prevent that occurring, and that therefore this particular technical detail is mostly irrelevant


  • I’m 90% sure it is not a single user. I just don’t see how that really affects the security of the product, given that the company that sells it can already do the things the author is saying can be done if you have this key.

    To be clear, I wouldn’t buy this. I just don’t think the SSH key makes it any worse than it already was




  • Sure, but then you’ve just shifted the problem up a level. Now I have to trust that the user id you provide me in the insecure channel really is you. Which means either trusting the insecure channel or trusting that the web app has confirmed who you are in some other way before giving you an ID.

    We have to reject the first since we could skip all the asymmetric crypt and just send a symmetric key directly in the insecure channel.

    If we’re trusting the web app has confirmed your identity, we’ve moved from “just quickly go to this page and it’ll generate you a public key” to “go to this site, upload a photo of your ID and a video of you saying that its you and whatever other verification is needed, then it’ll give you a public key”.

    You originally wrote:

    The one sticking point is that your recipient needs to visit the site before you can send your vacation photos to them, but is it really that hard?

    The hard part isn’t them going to the site in advance, it’s them establishing trust with the site that they are who they claim to be.






  • It’s a quite entitled view to take that they should make an effort to pass the project on. It would be very hard to build sufficient trust in a new developer quickly, and passing it on without that trust would be undermining the trust that users of the projects have placed in this dev. If I were him, I wouldn’t be staking my reputation on finding someone to take over from me if there wasn’t already an obvious candidate.

    The successful fundraiser you mention looks to have had a target of $12k USD (from: https://discuss.techlore.tech/t/divestos-is-unsustainable-needs-community-support-we-sent-250-and-you-can-help-too/6660, the original page has been taken down), and was as a alternative to them taking a full time job. I’d say its a reasonable bet that money was spent on living expenses, and IMO $12k a year is much less than this level of skilled work is worth. It’s certainly not enough money to make it unreasonable to shut down the project a year later, and I doubt anyone who donated feels shortchanged by it.