Just your normal everyday casual software dev. Nothing to see here.

  • 0 Posts
  • 150 Comments
Joined 3 years ago
cake
Cake day: August 15th, 2023

help-circle
  • You have correctly identified the core issue with open source.

    Personally speaking, as inefficient as it is, I think that donations is the best way to support a self hosted open source project.

    Followed by paying for licensing to be able to get support for the product.

    If your project is open source any other restriction out there, you can’t really do because they can just fork and patch the software to remove the restriction.

    Due to that restriction(or lack of), I’ve always personally seen most open-source projects to be more of a hobbyist or personal project then a project that someone wants to do to make money.


  • This happens whenever you’re talking about any topic that the AI model provider has decided arbitrarily they don’t want to do.

    I got temporarily banned off deep-seek the other day because I was curious about how well generation technology has gotten for self-hosting. So I asked it about setting up Comfy UI because I had never used it before. Woke up the next morning to a your account has been suspended because we have deemed you broke terms of service. In order to appeal you need a Chinese phone number, it made me chuckle.

    Considering the only two questions I asked it was about comfy UI or how to make a recipe similar to the now discontinued flaming hot cheetos Mountain Dew(I missed the production window sadly!)

    I’m leaning towards the comfy UI being the reason.

    edit: wrong software name







  • Yeah, I do agree your jurisdiction may vary.

    In the US at least, you can’t change a terms of purchase via a terms of service.

    So if it was stated at point of purchase that your system will be getting 10 years of updates, and then they decided six years in, you know what? We’re actually only going to do six years of updates, and then posted a terms of service that changed how long they were able to update it. That wouldn’t be legally binding.

    In this case, though it doesn’t sound like they’re changing existing buyer’s agreements, it sounds like they are changing the purchase agreement for new consumers who haven’t purchased the product. which is far more legally enforceable as no agreement has been done in that case.

    Still a shitty thing for them to do though, considering that they had promised that Chromebooks would have 10 years of updates but I don’t think they’re in violation of anything since it sounds like it’s only going to new consumers.










  • Said backdoor isn’t possible with the current day key exchange process. Without the servers in use private key, the most law agencies can do without acquiring the private key is force the CA to revoke a cert, which will disallow properly configured clients from accessing and transferring data with the server.

    LE doesn’t have enough information to recreate the private key based off the public key, the only key distributed during the CSR process is the servers public key via a certificate signing request which is signed using your private key, which the CA then signs with it’s own intermediate key (which is signed by it’s root server certificate) and hands back to the private server.

    The CA doesn’t have the ability to create that private key, and as such doesn’t have a way to decrypt traffic that is using that key. There is no concern for a backdoor in that process.

    In order for the “backdoor” to exist, they would need to either copy the private key as part of the signing process (which it doesn’t), or somehow force the server admin to use a new private key (that the CA also holds) or somehow compromise the servers key generation process to allow for an escrow on the private key when it was generated which would allow the CA to be able to recreate the private key using the master & public key.

    Now don’t take me wrong, you can still have a MiTM impersonation attack or a full impersonation bypass by the CA issuing a new certificate and having the DNS registrar have the web address go to a new server that is using the new key but, that’s not something the CA alone has the capability of doing, and any traffic that is issued to the original server still wouldn’t be compromised, its just clients visiting your site will end up at the other site and as such will end up using keys that the other side generated instead of your own keys and additionally said new keys would also be appearing in Certificate transparency logs, or modern day clients would refuse to use them.



  • Is this accurate? Like, I know what you’re meaning, but I’m pretty sure it’s not ICANN doing it, and more so your domain registrar handing it over to the US government.

    I think the most control that ICANN has over it is they could theoretically, if they wanted to, delete an entire top level domain. Since they do control the DNS root, but that is the most that they control from what I understand.

    I don’t know if they have the ability to delete or transfer control over an individual domain on legal request. I think that’s outside of what their actual system allows for.