🇮🇹 🇪🇪 🖥

  • 0 Posts
  • 111 Comments
Joined 8 months ago
cake
Cake day: March 19th, 2024

help-circle

  • Many encryption algorithms rely on the assumption that the factorizations of numbers in prime numbers has an exponential cost and not a polynomial cost (I.e. is a NP problem and not P, and we don’t know if P != NP although many would bet on it). Whether there are infinite prime numbers or not is really irrelevant in the context you are mentioning, because encryption relies on factorizing finite numbers of relatively fixed sizes.

    The problem is that for big numbers like n=p*q (where p and q are both prime) it’s expensive to recover p and q given n.

    Note that actually more modern ciphers don’t rely on this (like elliptic curve crypto).




  • sudneo@lemm.eetoTechnology@lemmy.worldWhat the hell Proton!
    link
    fedilink
    English
    arrow-up
    12
    ·
    1 month ago

    Encrypted DNS doesn’t solve everything. Handshake for TLS sessions is still in clear, you can usually see the SNI, and since we are talking about Wireless, usually this data is available to anybody who is in the vicinity, not just the network owner. This already means that you can see what sites someone is visiting, more or less. TLS 1.3 can mitigate some of this (for those who implement ESNI, but you don’t know that beforehand). Also TLS works until the user is not accepting invalid certificates prompts (HSTS doesn’t work for everything) and there are still tons of HTTP-based redirect (check mailing newsletters and see how many first send you to an HTTP site, for example) that can be used for MiTM attacks.

    A VPN moves the trust to a single provider that you can choose, which is much better than trusting every single WiFi network you can attach to and the people connected to it, I would say.

    Also if you pay for the VPN (I pay Proton), it’s not true that the company business is based on user data, they are based on subscriptions.


  • I can’t really make an exhaustive comparison. I think k3s was a little too opinionated for my taste, with lots of rancher logic in it (paths, ingress, etc.). K0s was a little more “bare”, and I had some trouble in the past with k3s with upgrading (encountered some error), while with k0s so far (about 2 years) I never had issues. k0s also has some ansible role that eases operations, I don’t know if now also k3s does. Either way, they are quite similar overall so if one is working for you, rest assured you are not missing out.




  • sudneo@lemm.eetoLemmy Shitpost@lemmy.worldHow to treat a man
    link
    fedilink
    arrow-up
    21
    arrow-down
    4
    ·
    3 months ago

    For too long it told men they can treat women however they want

    This is demonstrably false, as we have certain narratives that are literally millennia old (latin literature) about courtship, romantic gestures, protection and all the other stuff usually associated with how men should treat women. Usually this is some form of protection/care for a lower/weaker being, but it is absolutely a way society has been telling men how to tell women for centuries.


  • I would say that what you said applies not to feminism in general (who historically had strong links to class struggle and anticapitalism), but to a part of the modern status quo feminism which is focused purely on individuals and has been absorbed by the ruling class (e.g., once the CEO is a woman, the goal is reached). This is not a representation of feminism in general though, and I would say the same can apply to many other movements as well (e.g., ambientalism, antiracism, etc.) that (in part) lost their revolutionary nature and are left fighting for small changes within the status quo.


  • sudneo@lemm.eetoLemmy Shitpost@lemmy.worldHow to treat a man
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    3 months ago

    I think that in fact in at least some cases the lack of respect (or general ability to live a relationship with a man in a mutually loving way) is exactly due to that education. At the end of the day the flipside of the “subservient” attitude is that the man in the relationship is represented as a provider, with all the gender stereotypes that come with it: lack of emotions, self-reliance and of course the expectation for him to be a provider. I would say that most of the examples of bad relationships in this thread boil down to exactly these dynamics.

    Also we are not anymore in the 1950, so that education today mostly happens implicitly, but it also gets mixed up with a lot of other messages from the wider society.

    I personally also disagree about the fact that men are not taught how to fit in their gender role. I think they are, since very little, symmetrically to how women are too and possibly even more explicitly: you need to protect women (incl. sacrificing because that’s what heroes do), the whole courtship thing, the fact that as a man you are responsible to provide for others, that there are certain activities that are manly, etc… Essentially is the exact same problem: gender stereotypes and sexism go both ways and impact both genders, although in different ways.




  • You should definitely be! I take backups every 6h for my self hosted vaultwarden (easier to manage and to backup, but not official, YMMV). You can also restore each backup automatically and have a “second service” you can run elsewhere (a standby basically), which will also ensure the backup works fine.

    I have been running bit/vaultwarden now for I think 6 years, for my whole family and I have never needed to do anything, despite having had a few hiccups with the server.

    Don’t take my word for it, but the clients (browser plugin, desktop app, mobile app) are designed to keep data locally I think. So the term cache might be misleading here because it suggests some temporary storage used just to save web requests, with a relatively quick expiration. In this case I think the plugin etc. can work potentially indefinitely without server - something to double-check, but I believe it’s the design.


  • Interesting! That’s very close to this blog post I read long time ago (unfortunately medium.com link)! Are you actually sending emails from those addresses? Like if you need to drop an email to your bank, do you use the banking one or your personal (or something else)?

    Fwiw, I do something similar. I use a mix of domain aliases without address (e.g. made-up-on-the-fly@domain.com) and actual aliases. Since I have proton family (and the same when I used ultimate) I have unlimited hide-my-email aliases, so I have it integrated with my password manager, and I generate a random password and email for everything I sign up now. These though are receive-only addresses. In fact, with this technique I probably use 3-4 addresses in total, but I have probably 30 domain addresses that go to the catch-all one.

    Spam on these addresses are basically non-existing and you can still create folders based on recipient without having a full address (e.g. bank1@domain.com, bank2@domain.com). You can make folder categorization based on recipient regex and this way you also have the “stop bothering me” option: if some email gets into the wrong hands, you can create a spam rule for that dedicated address. However, my approach is that all of these are used just to receive emails, to send I have just a handful of actual addresses or -if really needed- I can create on-the-fly an address from a catch-all one, send the email and then disable it again (so it doesn’t count towards the limit, but I still get inbound email to the catch-all).

    Nice setup anyway!


  • Your requirements are totally fair tbh.

    That said, I think you can use aliases for the use-case you have, you don’t need full addresses. Proton supports “+ aliases” as well, so name+service@domain works, and most importantly they support catch-all addresses if you have your own domain. I now use actual aliases (the ones from simplelogin), which I generate on the fly, but if you can use whatever@domain and it will be redirected to your configured address. You don’t even need to create this beforehand, so many times I was around and had to give an email address for some reason and I just made up an address on the fly. As long as you use your domain, the catch-all will get the email.

    So the 10 addresses only include actual addresses, the ones you can write from. You can have as many as you want to receive emails (which is generally the use case for signing up to services, right?). Just a FYI in case tuta supports the same and you are making more effort than needed!



  • Encrypted or not, the fact that someone else has it stored somewhere in their computers is dangerous.

    Of course. You are simply over-representing this risk, though. Besides, regular people realistically don’t need to worry about Proton being backdoored, because their device is 10-100x more likely to be breached instead. Security is not a binary, it’s a shade. Performing a software update is also “dangerous”. Do you check every time you update the software its code, to verify no malicious backdoor is there? No, exactly, you trust the maintainers and the package infrastructure.

    The only recommended way to store private keys are offline and encrypted.

    So you don’t store them on your device(s) (encrypted)? I store my GPG keys that I use to sign software on my yubikeys. That said, email is something I check from my phone and multiple computers (as most people). Do you really use a hardware key to do on-the-fly decryption, every time someone sends you a message, from each device?

    As a security engineer, I also generally discourage such absolute “recommendations”. My threat model is different from a regular Joe threat model, and both are different from Snowden’s. There is no such thing as “only recommended way”, because this is not a religion, it’s a risk decision. Most people use Gmail, where the content of their email is literally available server side. Those same people can gain privacy and security using GPG via Proton, and in their threat model “provider gets compromised and software backdoored” is completely irrelevant. Is it relevant in your threat model? Good, then yes, you should only store keys offline and encrypted. Actually, you shouldn’t use email at all, and you should use dedicated tools and protocols that are meant for security, where metadata is not transmitted in clear text, for example. You should also have virtually no session duration and perform a full login with 2FA every time, you should probably access the software that you use to communicate only from a secure machine dedicated for the purpose etc…

    I think you trust Proton a bit too much.

    I simply have clear in my mind what my threat model is and what risks are acceptable. I perfectly fit in the “Anyone with privacy concerns” category in the threat model they built. What about you?