• 0 Posts
  • 12 Comments
Joined 3 months ago
cake
Cake day: August 12th, 2024

help-circle





  • “Evolutionary reason” does not necessarily mean that a feature is an advantage. Mutations are random and then positive or negative selective pressure act on them untill the mutation is either extinct or is adopted by the whole population. For features without selective pressure the same thing still happens it just takes longer and is basically random. So different populations of a species will always develop different features even when given the same environment.

    So for most of the features you listed: yeah it just happened.


  • You didn’t read the article did you? Its not about the inclusion of a character, but about how a specific scene with that character is handled. The author claims it is completely jarring, doesn’t fit into the games setting and doesn’t even use the games existing lore for transgender people but instead uses modern terminology.

    I found the article to very informative and not at all “gamergatey”.

    Its points are:

    • this is the scene
    • it is bad
    • here is exelent trans representation in a fantasy setting
    • “its a BioWare self insert”
    • this is how they could have handled it better
    • the game is great, but now everybody will just talk about woke, so again the game is good

  • E-Mail is old. So old that when it was invented, “hacking” and “security” was not really something anybody thought about.

    To send an email you connect to the recipients mail server and type in all the data of the mail. Including recipient, subject, mail body and importantly the address displayed in the “from” and “reply to” fields. They are all defined by the sender. The Email protocol has no way to verify if this information is correct and the sender is actually part of the aledged domain.

    Today, when you send a mail, most of the time you will not connect to the recipient mail server directly, but to a “sending” mail server, which then sends the mail to the recipient. For example if you log in to gmail, you write the mail on a google Mailserver which sends it to the recipient. Or you connect to your companies exchange through outlook.

    There is a modern extension to the mail protocol, which allows a domain owner to define the sending mail server which is allowed to send mails on behalf of this domain. But it is in the responsibility of the receiver to check. (Its called sender policy framework SPF)

    So most likely intuit didn’t do anything and the scamer just send mail without a sending mail server. And your receiving mail server did not verify the SPF correctly. Or intuit did not define an SPF. Or they did but it allows sources that do actually not belong to intuit but might be controllable by the scammers. This can happen if they want to send mails from cloud hostet systems and include them in their SPF, which may include systems by other customers of the cloud hoster.

    If you want to verify mail yourself, look in the mail headers (often called: view source) and look at the “received” headers. They deta the full path the mail has taken including which system initially wrote the mail. They are ordered bottom to top, so the (chronologically) first entry is the lowest. Check if the ip adress/hostnames for the first few hops belong to intuit and if they don’t, its most likely spam.

    TLDR: what is necessary to send mails from somebody else’s domain? Nothing. You can just do that. Mail is insecure by design and should be abolished.




  • groet@feddit.orgtoTechnology@lemmy.worldWhat the hell Proton!
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    1 month ago

    Client isolation doesn’t help. That is just the access point not routing traffic between connected devices. The problem with WiFi is it is a radio signal. Everybody in range can receive 100% of all communication on that network. Just by being in range the attacker can do passive sniffing. No wiretap needed like with cabled networks.

    WiFi is encryoed if it uses a password. So any public WiFi without a password can be sniffed by literally every device in range (no need to connect to the WiFi for sniffing). On public WiFi with a password, the radio signal is encrypted but everybody knows the encryption key. So everybody connected to the WiFi can still sniff the traffic of everybody else.

    That encryption is only on the WiFi level, so encrypted radio signals, not on the actually traffic level (like TLS/HTTPS etc).


  • groet@feddit.orgtoTechnology@lemmy.worldBe careful.
    link
    fedilink
    English
    arrow-up
    74
    ·
    2 months ago

    No, why would it? It will run code in the context of the current user which is absolutely enough to start a new process that will run in the background, download more code from a attacker server and allow remote access. The attacker will only have as much permissions as the user executing the code but that is enough to steal their files, run a keyloggers, steal their sessions for other websites etc.

    They can try to escalate to the admin user, but when targeting private victims, all the data that is worth stealing is available to the user and does not require admin privs.