Support the show by becoming a patron at tuxdigital.com/membership or get some swag at tuxdigital.com/store
Hosted by:
Ryan (DasGeek) = dasgeek.net
Jill Bryant = jilllinuxgirl.com
Michael Tunnell = michaeltunnell.com
Chapters:
00:00:00 Intro
00:00:42 Results of Michael’s Ratpoison Challenge
00:03:54 Community Feedback
00:15:13 Tech That Slipped Through Our Fingers
00:53:33 Canonical goes distro’less
01:02:03 New Sneaky Android Malware
01:10:32 Software Spotlight: Echo
01:13:13 Outro
Links:
- Results of Michael’s Ratpoison Challenge
- Community Feedback
- Tech That Slipped Through Our Fingers
- https://en.wikipedia.org/wiki/Neo_Geo_(system)
- https://en.wikipedia.org/wiki/Samsung_SPH-N270
- https://en.wikipedia.org/wiki/Google_Glass
- https://en.wikipedia.org/wiki/PalmPilot
- https://en.wikipedia.org/wiki/BlackBerry_Curve_8520
- https://en.wikipedia.org/wiki/Palm_Pre
- https://en.wikipedia.org/wiki/Atari_Portfolio
- https://en.wikipedia.org/wiki/Cray-1
- https://en.wikipedia.org/wiki/Cray_X-MP
- Canonical goes distro’less
- New Sneaky Android Malware
- Software Spotlight: Echo
The nickname of kubernetes is k8s because kubernetes starts with a k, ends with an s, and in between there are 8 letters.
that is a disappointing revelation but at least now I know
thanks
I’m sorry to tell you this, but Jill isn’t unhackable. Because “security through obscurity” isn’t security.
It might make it more difficult, but still very much possible. For the same reason you change the SSH default port to something else, to reduce your attempted login log-file. Not for actual security.
See also: https://wikiless.org/wiki/Security_through_obscurity
First, welcome back to the forum @RyuKurisu
and to respond to your comment, we don’t actually believe using floppies unhackable. With that said, Jill doesn’t just use floppy disks alone, the data on the floppies is encrypted and most of the time not connected to the internet due to the age of the hardware and there are other factors . . . however that is way too much stuff to put on a t-shirt ![:laughing: :laughing:](https://forum.tuxdigital.com/images/emoji/twitter/laughing.png?v=12)
First, thanks for sharing your thoughts on this episode and while my responses below may seem blunt, I want to be clear that I appreciate the feedback and it has made me revisit this topic so I can be better informed on future episodes.
This is fair, there have been many changes for the permission system of Android in the past couple of years. I do acknowledge this and thanks for pointing out the “full access” permission was remove. It should have never existed in the first place but good its deprecated.
I think it is also noteworthy that historically Android’s permission system has been not just bad but hot garbage for at least 12 years. I am happy to see them improving it but it still needs some work. The fact that a color control app for an LED light can require GPS permissions to function, not just request but require this permission is still hot garbage.
We didn’t say it was using the file system permission. We didn’t even say “file system permission” at all so not sure why you are complaining about “getting your facts straight” when we didn’t even say “file system”.
Okay sure, it’s 3 “Okay’s” instead of 1. Yes, it does warn the user and that is great but if this were an effective solution the issue wouldnt have worked so clearly this warning does not warn enough. I am sure the people who allowed it, did not read the message and simply pressed “Allow”. The minimum is text warning but the icon at the top should not be the app icon, this should be a large red warning icon. Yes, people ignored the warning and got infected but the warning is not sufficient and we both know that people would absolutely click that Allow without reading it. Yes, this is their fault but Google should change the icon to an actual warning icon at the very least.
Apple provides a lot of accessibility features themselves built in . . . but what are the functions that iOS doesn’t have that Android users can have because of this permission allowance? *Note - this is a genuine request for details
First, which is a better OS is subjective. Second, we never took a stance on which was best for accessibility. We said iOS’ permission system is more strict and that being a good thing. Accessibility was not in the discussion here so this argument has no relevance to what we said.
This is an analogy to a point we never made. However, I will respond anyway. This is much different since the Linux system requires sudo and your password to run this. “–do-what-I-mean” is not a real flag in rm, you have to type “–no-preserve-root” which is much more specific. Beginners wouldnt know what preserving root means but it might make them stop when seeing “preserve”. This also has to be done in a terminal which will scare some people from even attempting. So yea, this is not the same thing.
by the way, you probably mean the “do as I say” thing that Debian used to do but finally fixed making that much harder to do.
what apps are overwhelming valuable on Android vs iOS in this case? I am very curious.
Android is not an open and free ecosystem. Google requires the use of Google Play Services for a vast majority of Android features and all of the apps that were open on Android were closed by Google years ago, it is now just a skeleton system they offer in AOSP. I don’t know what your criteria is for calling Apple “oppressive commercial company” but I would bet whatever the criteria is probably also applies to Google just as much. Google used to be a company that I supported proudly and Android used to be the only platform I would consider and then they decided to do messed up stuff and drastically limit Android in terms of openness that it lost it’s credibility to be anything other than yet another massive tech conglomerate.
Continue the discussion at forum.tuxdigital.com
2 more replies