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

help-circle

  • Yes I read the article. I don’t agree with all the conclusions.

    Now is the best time to change to a new algo. SHA1 is not completely broken yet. It most probably will be at some point.

    Also AFAIK they will have compatibility tools for SHA1 repos in git. I don’t see the big deal with the path they chose.

    We will probably nor agree on that one. I think the hashes are important and that they are mutable right new with effort and later without. It’s okay that we don’t agree though. The git maintainers have made their decision anyways.


  • I have. In some languages you can use git repos as dependencies. It’s good practice to use hashes instead if tags because tags are not immutable. SHA1 hashes are better than tags but better hases would be even better.

    Also traceability. You can build a chain from your commit over ci to the artifact if you do it right. If you can change the files to a hash you can destroy that trust chain. Sha256 makes that impossible.

    People use the hashes in ways you might not. It wasn’t meant as a trust anchor but it became one. And that is now being addressed. I also think that the git maintainers have put a lot of thought into backward compatability and making the change as painless as possible.



  • Even if it’s not the purpose it can fulfill it. Hashes are used for all kinds of things like traceability or for pinning versions. They are used in a context where people depend on that a hash always has the same code behind it and SHA1 can not guarantee that anymore. A better hashing algo is needed to keep the way how people use git secure.

    It’s not enough to say “you shouldn’t use it that way”. We have to accept the reality of how git is used and adapt.













  • chris@l.roofo.cctoLinux@lemmy.ml•*Permanently Deleted*
    link
    fedilink
    arrow-up
    12
    arrow-down
    4
    ·
    3 months ago

    Most people don’t care, most distro developers seem to like it and I love it. Script based init system can fuck right off for me. Give me that opinionated goodness. Add some core system services. Make them compatible by default. Yes please. SystemD is where it’s at.


  • I used to be a gnome 2 user for a long time. I sometimes tried out KDE but it seemed to unstable so I moved back to gnome.

    But the problems started with gnome 3. I had never put much effort into customizing my desktop but I just didn’t like the defaults for gnome 3. Even worse some things I didn’t like were hard to change, some required plug-ins (that sometimes broke) and some just couldn’t be fixed at all.

    I could use my system but it always felt a bit like I did so begrudgingly. That was when I wasn’t using Linux full time. When I finally wanted to ditch windows completely I tried a lot. Different DEs, different distros and so on and I noticed that KDE felt good. I was skeptical but I gave it a real chance and I stayed. It feels good. It’s not perfect but I really like it. It is customizable enough but has sensible defaults. It doesn’t get in my way and I don’t use it begrudgingly.


  • You have to have so much more reserves in the US because of the broken health care system, and the car dependence. I live in Germany and my wife and I were thinking about how much more we’d need to save and we found out that we didn’t need that much. Healthcare is basically free, we don’t have a car, we had enough for a new set of appliances and months of rent. All that with about a half of that salary. But in the US you can easily go broke with that amount of money if you get sick or have car troubles. Also depending on the state poor job security.