steevdave's comments

steevdave | 6 years ago | on: More information about our processes to safeguard speech data

My experience with my Google home before I unplugged it is that it would randomly kick on - even in relative silence, unless the clack of a keyboard and maybe a fan whir could be misheard as "okay Google"

I would notice because it sat on my computer desk.

To be clear, I don't think it was nefarious that it would, just that I realized I wasn't using it as much as I thought I would and decided to unplug it.

steevdave | 6 years ago | on: Gokrazy: a pure-Go userland for Raspberry Pi 3 appliances

wpa_supplicant just does the heavy lifting of connecting to the WiFi network.

The WiFi device itself is handled by the kernel's brcmfmac driver, and there is the usual firmware (also requires a .txt file) or you can use something like nexmon, which tweeks the firmware (and a patched driver to use it) for using monitor mode, injection and a few other misc things people have done with the firmware.

steevdave | 6 years ago | on: Raspberry Pi 4

Are you sure? I've worked with a myriad of ARM devices, and I would say that despite their small size, Hardkernel are one of the most responsive companies when I have had issues.

I say that as both a Gentoo and Kali ARM dev

steevdave | 7 years ago | on: The Raspberry Pi store is much cooler than an Apple Store

Just about every other board out there is just as plug and play as the RPI.

I'm not saying that to downplay the RPI - the community it has around it is great, but long gone are the days of trying to get Linux running on a random arm board. And I should know, I have over 100 different arm machines at my place.

steevdave | 7 years ago | on: A timesyncd failure and systemd's lack of debugability

The lack of contributors has a lot to do with Lennart's (apologies if I misspelled his name) attitude early on in systemd's development.

I have no idea if it has changed, as I gave up trying to get things fixed.

The one issue I still have with systemd is the way it handles the kernel's command line.

I work with Chromebooks a lot, using software that isn't ChromeOS. The cool thing is that they can use FIT images so you can load multile kernels and device tree bindings into one image. So I can use the same sdcard on the Acer tegra Chromebook, Samsung's Chromebook, as well as the ASUS Flip Chromebook. However, to boot from sdcard you have to enable developer mode. When you enable developer mode, it adds a flag to the kernel command line "debug" - systemd sees that and thinks you want systemd in debug mode (wat?) Unfortunately there is no way to override this. I've tried passing the log level as info, which sort of works, until journalctl starts, and IT parses the debug flag in the command line and ignores the flag that sets the log level to info.

No amount of explaining this helped and I (and many others who have had various issues) gave up on trying to help make systemd better.

The only workaround to this is to stop using 1 sdcard amongst all of my Chromebooks and use individual sdcards per machine that uses a u-boot built for each Chromebook that does not pass the debug flag.

I like systemd and many of it's features are helpful, but when you run into issues, it's almost always an uphill battle to fix them, even when you provide a patch.

steevdave | 7 years ago | on: Pi-Hole: Why You Need a Network-Wide Ad-Blocker

Maybe they added it after you read it, but when I read the post they specifically mention it's bad and provide a link to read more on why it's bad.

Sure an alternative would be great but the point of the article is to get up and running with the pi-hole software so they went with the fastest install.

steevdave | 8 years ago | on: Exploiting the Wi-Fi Stack on Apple Devices

Anything iPhone 5 or lower will not - 10.3.3 fixed one of the issues, but 2 more exist.

I do wish they would at least put out a 10.3.4 to fix the security issues, but I understand not putting the resources into a phone from 2012; I'm happy to at least have gotten 10.3.3 considering my Nexus 5 stopped getting updates last year and it was release in 2013.

steevdave | 8 years ago | on: With a $1k Price, Apple’s iPhone Crosses a Threshold

It takes only one slip up to screw your security. One targeted attack that you don't notice because you're in a rush.

I love my MotoX 2013, but it never got updates (Sprint model, Sprint blamed Motorola, Motorola blamed Sprint); it's succeptible to Stagefright so I can't use it anymore. And it will never receive an update for it.

As much as we use our phones and as much personal information is on them, security updates should be first and foremost.

Yes, AOSP exists for some devices, but 9 times out of 10, something breaks when using it.

When Android moves to a new way of doing audio or video, drivers stop working, and some people try to come up with shims, but as others point out. The developer of it gets a new phone and the project dies.

My Nexus 5 (November 2013) hasn't gotten a security update since October 2016. My iPhone 5 (September 2012) just got an update to 10.3.3 in July.

Android devices are notorious for being slow to get updates, if you ever get them at all.

Yeah it can be cheaper to get an Android device, and I have quite a few, but they simply aren't up to the same standards that iPhones are.

page 1