• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle

  • It’s just one of many private ranges.

    Sure, it’s one of many, but how often do you see that specific (42) block used? I honestly don’t think I ever have, outside of a pentest lab. The 172.16.42.0/24 (not just any 172.16 like you’re saying) block is the default for a WiFi Pineapple. Any other range is usually ok, but the 42 on a /24 granting WAN access specifically would make me (and most people who actually know what a WiFi Pineapple is) avoid that network.

    Saying 172.16.0.0/12 is usually for pentesting scummy thing is very misleading…Saying it’s dangerous is like saying every websites using .xyz domain is dangerous(which makes little more sense than this, btw)

    You clearly don’t know what a WiFi Pineapple is, because we’re zeroing in on the 42 and you liken it to the entire 172.16 block. And linking every .xyz domain to a specific block (42) that is used by default for a pentest device is even more misleading.


  • There’s nothing at all suspicious about the 172.16.0.0/12 address block.

    Correct. However the 172.16.42.0/24 block is the default for a WiFi Pineapple. Any other range is usually ok, but the 42 on a /24 specifically would make me (and most people who actually know what a WiFi Pineapple is) avoid that network.



  • if used for work…Features? Don’t care.

    Most organizations care about maintaining document compatibility, especially formatting, and that usually means Office365. Microsoft is notorious for publishing a standard and then ignoring their own standard, making it exceedingly difficult to use other office suites.

    I’ve heard OnlyOffice does the best at maintaining compatibility.







  • To be fair, the Aiel didn’t initially grow up there (and too short for evolution, in my non-scientific brain), but rather migrated there to use it as “a shaping stone to make them, a testing ground to prove their worth, and a punishment for their sin.” And it would be too easy on those three reasons if they were perfectly (or mostly) acclimated and suited for the desert genetically.


  • People used to got to Custom ROMs because OEMs were really doing shit job, that’s not the case now given now.

    Yep. I used to use custom (ROMs, kernels, etc) for the extra features and playing with my phone like a shiny new toy. Now I use GrapheneOS because OEMs and Google don’t do security and privacy anywhere near as good as GOS. And I can live with the minor inconvenience of apps that use Play Integrity API, though I do encourage the app devs to switch to hardware backed attestation because: “Android’s hardware attestation API provides a much stronger form of attestation than the Play Integrity API with the ability to whitelist the keys of alternate operating systems. It also avoids an unnecessary dependency on Google Play services and Google’s Play Integrity servers.” https://grapheneos.org/articles/attestation-compatibility-guide


  • occupying valuable storage space

    I can’t remember last time in the past 5 years, maybe full decade, where I was running low on storage space on a smartphone.

    consuming bandwidth, and draining battery life

    If they’re truly forgotten and this not used, Android places them in hibernation. At a certain point, Android disables then and removes any granted permissions.

    their icons present while the app itself is not actually installed. They would remain dormant until needed, at which point they would be automatically downloaded and launched.

    This just sounds like a bookmarked PWA website…which I actually always recommend when available. PWA are less intrusive and less permission hungry than the typical app.