• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle

  • I agree because it is exactly what my claim is. It would still be foolish to say that open source software is by design more secure than proprietary. I know that this is not what you said and you most likely also don’t mean that, but there are enough people who think that way because they read everywhere that OSS=secure software.

    Your example with xz however does not really hold imo. The xz bug was not found because xz is open source but because someone realized, that their ssh session build up took longer than usual and they then used valgrind to check for issues and not because they looked in the source code. It wasn’t even really an easy to spot backdoor because it was a malicious compressed file that changed the build process while running the tests and injecting the actual backdoor in the compiled file. Therfore this would have been found with proprietary software with the same likelyhood.

    And regarding my analogy: I also like it more when things are recyclable, that is also why I like open source software more and have more trust in it. But now that I think about it, that wasn’t the best analogy I could’ve chosen but it was the first thing that came to my mind.


  • Could we please stop associating open source with security? Don’t get me wrong, I love open source software and it is easier to trust open source software than proprietary, because it is highly unlikely, that they hide stuff like trackers in there. It is also most of the time highly configurable and sometimes even hackable and as a software developer you are able to look into the mechanisms behind the APIs which is sometimes really helpful.

    But events like the lzma incident last year and predictable openssl RNG in Debian some time ago (https://lists.debian.org/debian-security-announce/2008/msg00152.html) should tell us, that open source doesn’t mean secure software. And the argument, that there are many people looking at the code is not really true. E.g. many maintainers of the linux kernel only look at specific parts/drivers in it and maybe into some other things they need for that. There are probably only a few people if any (apart from governments), that have read, understood and analyzed the linux kernel in its entirety with all the (open source) drivers built into it and all the possible combinations of configurations. And I don’t want to know how many have done all that for less popular projects. And even if that is done at some point for an upstream project, you would have to check the patches from your distro and if there are any do it all for yourself again. And when the next release arrives you would have to do all that in its entirety again (although with some head start) if a new version arrives (that has, say, at least a thousand lines of code changed, removed or added). And now think about how many big releases come with some software per year. And don’t forget to also include all the dependencies you have to check including the compiler and standard library of the language(s) used.

    Of course it is easier to do all that for OSS as an outside party because you don’t have to decompile it, but it is still increadibly hard. And only to be easier to analyze for security risks doesn’t mean to be more secure just like packaging being recyclable doesn’t mean that it will be recycled.


  • Yeah, it really is more like google play store or shopping websites and similiar apps/websites (although there are some that have a better design I guess). I’m not really a fan of it either, but I guess people being used to those (which is probably the majority of the userbase of flatpak) feel more comfortable with it.

    My guess with the difference between “trending” and “popular” is that the former means lots of recent downloads and the latter a lot of downloads in a longer timespan (e.g. a year or so)




  • A very important one besides backing up your files is that you should more or less stop searching the web for applications to download and install. You should first try to use your package manager (read the wiki of your distribution to know which one it is and how to search for and install software with it). If you miss some applications from Windows, you could have a good chance to look for alternatives at sites like https://www.opensourcealternative.to/

    Do not fear the terminal too much. I know, Windows tried to make it as dreadful as possible to use, but if you do not run sudo rm -rf / (deletes your whole filesystem), there is not much that can go awfully wrong. And you should only execute commands you understand. If something does go wrong however, it is a good thing to have a backup ready (I would recommend Pika Backup or Vorta, both based on the great CLI application borg)

    For things that are not explained in the wiki of your distro, you have a pretty good chance to find a good explanation and even troubleshooting tips at the Arch Wiki (e.g. I use Void Linux and still search for most things at the Arch Wiki). It is also good to read some parts of the manual pages if you did not find enough information at the Arch Wiki (the command man is your friend) and the software’s wiki page if it exists.

    If you ever find yourself in the editor vi or vim, type :q and press enter to quit until you feel the need to potentially invest a lot of time in learning vim movements to increase your editing speed and you never want to go back. Use nano, micro or a graphical app at first instead and keep using it if you are not someone who edits text a lot.


  • For the purpose of algorithm verification, the final and/or pushdown automaton or probably sometimes even Turing Machines are used, because they are easier to work with. “Real” regular expressions are only nice to write a grammar for regular languages which can be easily interpreted by the computer I think. The thing is, that regexs in the *nix and programming language world are also used for searching which is why there are additional special characters to indicate things like: “it has to end with …” and there are shortcuts for when you want that a character or sequence occurs

    • at least once,
    • once or never or
    • a specified number of times back to back.

    In “standard” regex, you would only have

    • () for grouping,
    • * for 0 or any number of occurances (so a* means blank or a or aa or …)
    • + as combining two characters/groups with exclusive or (in programming, a+ is mostly the same as aa* so this is a difference)
    • and sometimes some way to have a shortcut for (a+b+c+…+z) if you want to allow any lower case character as the next one

    So there are only 4 characters which have the same expressive power as the extended syntax with the exception of not being able to indicate, that it should occur at the end or beginning of a string/line (which could even be removed if one would have implemented different functions or options for the tools we now have instead)

    So one could say that *nix regex is bloated /s


  • Those not using it are playing with their computers.

    What is your definition of playing? I use it to code, access my server for some self-hosted services, do office stuff and sure, also for gaming and watching videos. Am I disallowed to wanting to develop at ease with a minimal setup compared to windows and avoid shit like forced cloud stuff because I am gaming on this os? Isn’t it my choice and compliant to free and open source software to have the freedom to use the OS one has the best experience with?

    About the gaming stuff: As I have said, I am just currently converting to wayland, so I don’t know of issues because I haven’t tried linux native games extensively. Wine doesn’t have working wayland support but is still (in my short experience) working with xwayland. Linux native games I will try soon are Cassette Beasts, Stardew Valley and maybe Cross Code at some time, all actually native games.


  • Why do you think waypipe should be the most important thing? Sure remote graphical sessions are neat but there are only a few people who really need it or not? At least I do not see how this is really that beneficial on linux compared to just basic shell stuff that most people are using when doing something remotely. Maybe it is something that the big businesses are using but then there will probably be a discussion to really add it to the protocol directly (if that is even actually needed, waypipe is a software stack that works (with limitations) with the current protocol; wayvnc for wlroots-based compositors seems to work fine and gnome and weston also implement some kind of RDP)

    Also, what do you mean “it is made for gamers who can’t be bothered to stand up for linux native games”? Are there actually that many issues with xwayland for native games until Wayland support is added, just like using the pulseaudio server for pipewire until pipewire is completely supported? I am currently slowly transitioning to wayland so I don’t know if there are actually any so please tell me if it is the case or if I am missing something.




  • Ok so this will be the last comment on this thread, I just want to make one final thing clear and I suggest that we get out of our way afterwards.

    I totally understand, that selling data to third parties is a bad thing, but even your cited site doesn’t claim, that valve sells one’s private data to third parties and their privacy policy also doesn’t state it (at least the german version I have read through), even more they explicitly state in 5. that they don’t sell data to third parties. They only state that they give it to third parties where they more or less have to.

    Now one has to decide if they trust valve to hold on their own PP but that is always the case for every platform, even open source ones,because again, no one can easily verify, that they don’t do shady business with your data, because they won’t give you ssh access for obvious reasons.

    Don’t get me wrong, I am pretty paranoid as well: I don’t use any Microsoft products anymore (except minecraft), I stay away from Meta and Google as well by using e.g. signal and matrix for communication and have lineage on my phone, I use noscript because I don’t trust every website’s JavaScript and host my own instances for gaming servers, git and other stuff on my netcup server.

    But I step out at some point where convenience wins over more privacy and security. I don’t package and compile everything myself, have verified the souce code before myself, because I trust the maintainers. I don’t have a completely open hardware PC, where I have built and verified everything myself, because I trust chosen manufacturers that they haven’t tampered with it (and don’t have the time or even money to do that).


  • Ok so first of all, “everyone” is restricted to you and stappern. Now what’s the difference between you two? Stappern made actual good and valid points and got me convinced a bit more to stay away from steam as much as it is possible for me in my situation without even insulting me once. If you really think you could get others convinced of your opinion by just insulting them, then I think it would be cool for you to call you stupid.

    And that the comparison between doing something that reduces your lifetime and overall quality of live vs. giving others the data they need to stay in compliance with the various legal systems and get you the things you bought WITH money (because you seem to also understand downloading foss software as buying), is so farfetched that it’s even crazy to come up with, should be clear.





  • The criticism itself is not. Throwing assumptions like “you are an addict if you continue to use this platform no matter what your reason is” (which is what I read out of this person’s comment) around is also not preventing anyone from enjoying things. I just thought that specifically this assumption was overshot and it read like a straight up insult. I do get it now at least a bit although especially because they just insulted me without any arguments, I still guess that they just insulted people and not gave them a diagnosis of an addiction.