• 0 Posts
  • 11 Comments
Joined 3 years ago
cake
Cake day: June 14th, 2023

help-circle

  • It might be the end of GPL-type licenses. But, at least as far as I’ve understood it, the point of copyleft was to use copyright against itself in the first place, because copyright sucks, and at the end of the day we don’t really want copyright OR copyleft. They’re both asserting “ownership” of stuff that honestly belongs in the public domain free to all humans to use (in an ideal world, that doesn’t contain evil corporations that are considered people for some reason). We already know copyleft open source has been widely abused in proprietary software. This is not new nor surprising. We gave them the richly deserved middle finger whenever we could find out they did it before, and we hate it, but it was never “the end” of open source software because making it publicly available is precisely the defiance we are ultimately aiming for and we will always do that no matter how much they steal it and make it closed source.

    People making closed source software are the enemy, and our war of freedom against them continues regardless of what tactics they use to demean our efforts while they make their closed source software. We will never let them win. They think they’ve found a new way around the GPL, that’s a shame, but so be it. The arms race will continue, but open source will not go away, because the point of it has nothing to do with meekly relying on the law to allow open source to exist, that’s just a method that has been used, with some success, and allowed a lot of people to turn it into a livelihood, and it will be a terrible shame to lose that.

    Those things are not the true goal of open source though. The intention of open source, is to not let proprietary, hidden software dictate the fate of humanity and we will do it for as long as we have to. We’ll do it if we’re protected by copyleft, we’ll do it if we’re not. We’ll still do it even if they make it illegal, and we’ll call it reverse engineering, hacking, and piracy if we have to. Because the information and code that humanity relies on must be free, not owned.









  • cecilkorik@lemmy.catoSelfhosted@lemmy.worldWhat do I do -- Incorrect?
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    9 months ago

    Aha I see you did the text-based install then? I’ve never done that myself but I just tried it now and it worked fine for me with the default password it mentions. Make sure caps lock is off. You will not be able to see the password when you type it, so be extra careful you are typing it correctly.

    Most of the same cautions about internet access still apply, if your networking is active on this VM there’s a non-zero chance you can get hacked right away when you’re in default passwords/initial setup mode. If you continue to have trouble getting in, you should reinstall it once again onto a fresh VM with network mode set to NAT if possible, or even disabled completely, and see if it works in that configuration. It really is critical to get the password set up before opening up the internet.


  • Not sure what you mean by “what was provided”… who is providing a username and password for your yunohost?

    You are supposed to create your own username and password during the “Begin” setup process after it first installs. “root” and “yunohost” are very insecure and if you use passwords that are copy/pasted from somewhere else on a machine connected to the internet it will be hacked, potentially almost immediately. People have bots that literally just try to connect using these common default passwords all day every day to every site on the internet. I have literally had machines with such crappy passwords hacked within minutes of spinning them up. The same thing can happen even when you are first doing the setup process. If somebody else can get in, they can (most likely with a bot) do the setup process themselves and set up their OWN username/password, and now it will ask you for that password that THEY set, which you have no way of knowing. The instance belongs to the first person to claim it, and if that’s not you, you have to wipe it and start over.

    Your yunohost VM interface should not be exposed to the internet during setup. Even briefly, or someone else can immediately compromise it like this. The only way to ensure you are the first person to access it is to make sure you are the ONLY person who can access it, until it is properly set up and secured. Bots are WAY faster than you can be.

    Use localhost console, VM port forwarding or some other secure method of making sure nobody but your own host computer can access the IP of the server where you are setting things up, until it has a strong, secure password (not “yunohost”) and make sure you have all its security features configured and working before you even think about making it accessible to the internet.