• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: November 26th, 2023

help-circle
  • From what I can find, by “These routers send your credentials in plaintext”, they actually meant to say, “The mobile app sends credentials in plaintext.”

    If you use the web interface then your credentials are not sent in plaintext. The routers themselves also don’t send credentials in plaintext.

    The people who found this out got that wrong, and a lot of people are confused because they didn’t expand on “in plaintext.” They could be a little more professional / thoughtful.

    Edit: I’m also thinking about the “may expose you to a MITM” bit. I think if it was https then a MITM (assuming all they can do is examine your packets) wouldn’t work because the data can only be unlocked by the private key. It sounds like it was an http connection?








  • It’s new to me, I think it’s saying that your system is built up by you declaring what you want in a file, a single source that everything comes from.

    It’s atomic because each action the system takes is carefully completed rather than bailing out and requiring you to fix something.

    It’s immutable meaning you declare how you want things to be set up and then critical changes stem from those declarations and nothing else. You would obviously generate preferences, save data, etc. but the files that make the system / packages work are carefully locked.

    It’s like the concept of flatpaks + structured system defining + modern common sense OS operations?




  • You use lifetimes to annotate parameters and return values in order to tell the compiler about how long things must last for your function to be valid. You can link a specific input with the output, or explicitly separate them. If you don’t give lifetimes the language uses some basic rules to do it for you. If it can’t, eg it’s ambiguous, then it’s a compile error and you need to do it manually.

    It’s one of the harder concepts of rust to explain succinctly. But imagine you had a function that took strA and strB, used strB to find a subsection of strA, and then return a slice of strA. That slice is tied to strA. You would use 'a annotation for strA and the return value, and 'b for strB.

    Rust compiler will detect the lifetime being shorter than expected.


    Also, ownership semantics. Think c++ move semantics. Only one person is left with a good value, the previous owners just have garbage data they can’t use anymore. If you created a thing on the heap and then gave it away, you wouldn’t have it anymore to free at the end. If you want to have “multiple owners” then you need ref counting and such, which also stops this problem of premature freeing.


    Edit: one more thing: reference rules. You can have many read-only references to a thing, or one mutable reference. Unless you’re doing crazy things, the compiler simply won’t let you have references to a thing, and then via one of those references free that thing, thereby invalidating the other references.



  • mhague@lemmy.worldtoProgrammer Humor@lemmy.mlThanks ...
    link
    fedilink
    arrow-up
    4
    arrow-down
    20
    ·
    6 months ago

    I don’t see a negative. It’s foss so you ought to be relaxed about others using your code. The issues are probably just articulating problems that were already there. If it’s stuff you don’t care about… it’s a foss repository so you just ignore it.