• 3 Posts
  • 37 Comments
Joined 11 months ago
Cake day: December 26th, 2023
  • sighofannoyance@lemmy.worldtoTechnology@lemmy.world•YouTube to eliminate 100 employees as layoffs at Google continueEnglish
    21·
    10 months ago

    layoffs would not be the bellwether for that.

    I guess we can at least agree, that even if a company doing lay offs isn’t necessarily going belly up, a company that is going belly up is probably doing some lay offs along the way.

    However going beyond the point we agree over… what if a lay off sets in motion a series of chain reactions:

    • reduced investor/shareholder confidence -> possibly stock/company-value tanking -> -> leading to issues with the lowered valuation and their debt, worse credit rating(?)
    • destroyed worker moral -> the best workers are more likely to leave, workers who remain having to shoulder their burden
    • less team members have to shoulder much more work (usually for the same pay)

    I am sure there are other factors and maybe some of those three above are not a factor at all…

  • sighofannoyance@lemmy.worldtoTechnology@lemmy.world•Wi-Fi 7 quietly took off while everyone was looking at AIEnglish
    21·
    10 months ago

    https://en.wikipedia.org/wiki/KRACK " The KRACK attack

    believed to affect all variants of WPA and WPA2; however, the security implications vary between implementations, depending upon how individual developers interpreted a poorly specified part of the standard. Software patches can resolve the vulnerability but are not available for all devices.[57] KRACK exploits a weakness in the WPA2 4-Way Handshake, a critical process for generating encryption keys. Attackers can force multiple handshakes, manipulating key resets. By intercepting the handshake, they could decrypt network traffic without cracking encryption directly. This poses a risk, especially with sensitive data transmission.[58]"

  • sighofannoyance@lemmy.worldtoTechnology@lemmy.world•Wi-Fi 7 quietly took off while everyone was looking at AIEnglish
    61·
    10 months ago

    https://web.archive.org/web/20151113152528/http://www.airtightnetworks.com/WPA2-Hole196

    "the group temporal key (GTK) that is shared among all authorized clients in a WPA2 network. In the standard behavior, only an AP is supposed to transmit group-addressed data traffic encrypted using the GTK and clients are supposed to decrypt that traffic using the GTK. However, nothing in the standard stops a malicious authorized client from injecting spoofed GTK-encrypted packets! Exploiting the vulnerability, an insider (authorized user) can sniff and decrypt data from other authorized users as well as scan their Wi-Fi devices for vulnerabilities, install malware and possibly compromise those devices.

    In short, this vulnerability means that inter-user data privacy among authorized users is inherently absent over the air in a WPA2-secured network. "

    https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access#Security_issues

    " Predictable Group Temporal Key (GTK)

    In 2016 it was shown that the WPA and WPA2 standards contain an insecure expository random number generator (RNG). Researchers showed that, if vendors implement the proposed RNG, an attacker is able to predict the group key (GTK) that is supposed to be randomly generated by the access point (AP). Additionally, they showed that possession of the GTK enables the attacker to inject any traffic into the network, and allowed the attacker to decrypt unicast internet traffic transmitted over the wireless network. They demonstrated their attack against an Asus RT-AC51U router that uses the MediaTek out-of-tree drivers, which generate the GTK themselves, and showed the GTK can be recovered within two minutes or less. Similarly, they demonstrated the keys generated by Broadcom access daemons running on VxWorks 5 and later can be recovered in four minutes or less, which affects, for example, certain versions of Linksys WRT54G and certain Apple AirPort Extreme models. Vendors can defend against this attack by using a secure RNG. By doing so, Hostapd running on Linux kernels is not vulnerable against this attack and thus routers running typical OpenWrt or LEDE installations do not exhibit this issue.[54] "