• 3 Posts
  • 474 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle






  • I feel like people need an education about the difference between spirit of the law and letter of the law.

    This comment reads like this:

    “I posted some truly heinous shit and a mod/admin removed it but I didn’t break any written rules therefore my right to force other people to be subjected to my desires was impinged upon😭😭😭😭.”





  • Using Kali? Easy if you have training. The capstone for our security course a decade ago was too find and exploit 5 remote machines (4 on the same network, 1 was on a second network only one of the machines had access to) in an hour with Kali. I found all 5 but could only exploit 3 of them. If I didn’t have to exploit any of them 7 would be reasonably easy to find.

    Kali basically has a library of known exploits and you just run the scanner on a target.

    This isn’t novel exploit discovery. This is “which of these 10 windows machines hasn’t been updated in 3 years?”




  • The issue is that multiple winners split the jackpots, which is why playing common numbers like dates (birthdays) is a terrible strategy since so many people play those.

    When the Powerball exceeds the value of being able to purchase all of the numbers it is common that the number of tickets sold more than doubles the Total number of numbers which statistically guarantees multiple winners. Almost nobody wins those billion dollar jackpots by themselves.


  • Separation of data between accounts makes them fall under different retrieval requirements.

    As one account, a request for all of the data from that account contains both chunks. Separation of those accounts separates the need to accommodate requests for data from one on the other.

    It can also mean that internally they may have a sufficient mechanism that data that was previously identifying to no longer being identifying (breaking userid to data pairings for example) which is sufficient to “anonymize” the data that it no longer needs to be reported or maintained.


  • GDPR and pii reasons most likely. It’s a nightmare keeping track of why certain data is on certain accounts. This can vastly simplify the GDPR compliance mechanisms. If your GOG account is merged with your PR account, there is probably significantly more “sensitive” data (CC numbers, addresses, etc) in the GOG account. This probably exempts some data that either cdpr or gog tracks from deletion or retrieval requests.



  • There is probably an opportunity in this space to provide ultra low cost single board SPA/elctron serving applications. But getting it adopted is going to be an issue.

    A good industrial engineer is going to look at it kinda suspiciously. Kinda like how Tesla got rightfully raked over the coals for trying to use consumer grade electronics in cars and their screens started melting as well.



  • Who are they going to pay to maintain FLTK? There are still companies that are adverse to using Linux because they don’t know what is going to happen when Linus dies. That might sound strange to us, but companies need legal protections that they can enforce through contracts and support contracts make that happen.

    The laggy bit can be explained this way: all of these decisions are made because in theory this all sounds “right” (to the company) but then they get their prototype out with a medium level hardware solution and they look for places to squeeze. Oh, you mean I can take this half price min spec machine and it works 98% of the time? Sold.

    Im not trying to say these are good practices, I am trying to explain the decisions that are made.