henfredemars

joined 1 year ago
[–] henfredemars@infosec.pub 63 points 13 hours ago (3 children)

I don’t think it really matters what is legal at this point because we cannot hold him accountable anyway.

[–] henfredemars@infosec.pub 12 points 13 hours ago

I didn’t think they were going to eat my babies.

[–] henfredemars@infosec.pub 6 points 13 hours ago (1 children)

Best get used to it. It’s going to be tough for a while.

[–] henfredemars@infosec.pub 50 points 13 hours ago

It’s the risk you take. I’ve met some of the most interesting people this way. If you go into it with an open mind and understand that usually it’s not going to work out, you’ll be better for it.

[–] henfredemars@infosec.pub 27 points 13 hours ago (1 children)

Let’s see it then. I’m concerned when the opportunity to profit arises that perverse motives will occur.

[–] henfredemars@infosec.pub 9 points 1 day ago

Don’t worry. You’ll get the rest of the little ones with your feet.

[–] henfredemars@infosec.pub 6 points 2 days ago

Ain’t half bad.

[–] henfredemars@infosec.pub 50 points 2 days ago* (last edited 2 days ago)

In principle, yes, and I believe a few small hobby projects have attempted to do this and support specific TVs. However, interest in developing a custom Smart TV platform tends to get siphoned away into a project where the output from your actual platform is displayed on the TV rather than running directly on it. Simply, it’s easier to develop and maintain support across different models.

Why would you develop a custom TV OS that runs on one TV when you could develop it for any mini PC and immediately support all TVs? You’d have to develop your OS to run on each specific TV model which will make it quite hard to reach a critical mass sufficient to attract attention from developers and users alike.

The juice isn’t really worth the squeeze. It’s not like TV vendors are publishing detailed hardware specs and drivers. Writing or even porting an OS is hard. Look at the state of the Android ROM scene, and that’s about as good as it gets when some vendors are actually attempting to open source their drivers. The difficulty is much higher and the interest lower due to the existence of a viable alternative.

With that said, motivated minds have done it anyway. You just need to have the right TV for it.

[–] henfredemars@infosec.pub 10 points 3 days ago

Most of ours used to be white!

[–] henfredemars@infosec.pub 5 points 3 days ago

He’s into it.

[–] henfredemars@infosec.pub 15 points 3 days ago (1 children)

I would but I rather stay in my lane.

The joke is that BMW drivers don’t use their blinkers and may not give notice of quitting a job.

[–] henfredemars@infosec.pub 6 points 3 days ago (1 children)

I’m sure it’s been asked 1 million times but do they actually federate with us? I haven’t seen a blue sky handle.

 

Another shameless theft of title and meme, unknown source. To add a personal touch: my bro just started a job with an insurance company where they talked him up about all the cutting edge work they're doing in AI, ML and statistical analysis. Yeah, it's just a bunch of Python scripts calling out to web services. They should have just said they're looking for a (possibly backend) developer.

486
Programmers Contest (infosec.pub)
submitted 2 weeks ago* (last edited 2 weeks ago) by henfredemars@infosec.pub to c/programmer_humor@programming.dev
 

Shamelessly stolen from Reddit. No source in the original post.

 

This article goes into more detail about how these new measures will actually work compared to the blog post earlier this year from Google. Namely:

  1. Enabling the OEM unlocking setting will no longer prevent FRP from activating.
  2. Bypassing the setup wizard will no longer deactivate FRP. FRP restrictions will apply until you verify ownership of the device by signing in.
  3. Adding a new Google account is blocked.
  4. Setting a lock screen PIN or password is blocked.
  5. Installing new apps is blocked.
 
48
Adding 16 KB Page Size to Android (android-developers.googleblog.com)
 

In this post, we’ve discussed the technical details of how we are restructuring memory in Android to get faster, more performant devices. Android 15 and AOSP work with 16 KB pages, and devices can now implement 16 KB pages as a development option.

 

I have a large DVD collection containing lots of niche titles that don’t appear to be on any public tracker. I would like to share my love of these films with the world.

I have access to a server that’s online 24/7 with a symmetric link and no data cap. My plan is to use a docker container with a web transmission instance to seed all of my material through a VPN provider (for my own safety). My server was last rebooted 200 days ago; I intend to rack lots of uptime seeding with my server. I have technical skills and I can ensure I’ll have an open port to accept connections.

Questions: what steps should I take to protect myself in seeding these DVDs? Is there a guide or some recommendations you can provide to get the best quality out of the many hours I’m going to spend ripping? Is it possible to trace the DVD reader that made the rip? Are the cool kids still uploading torrents or is there a better technology I should be using?

Overall, I have plenty of content to share, but I don’t want to put myself at risk when I do.

 

Article refrains from drawing conclusions, instead presenting the data. Android is doing better at moving users to newer versions, but the overwhelming majority of users don't have the current Android OS version nor the previous version, combined.

 

Bullet points stolen from the linked article:

  • Code suggests the satellite connectivity feature on Pixel devices could be called “Pixel Satellite SOS.”
  • We’ve also found a clue suggesting that the feature will be offered for free for two years, which would match Apple’s current offer on the iPhone 14 and 15 series.
 

I want to share this post because I was disappointed to see this popular smartphone cracking tool works very well across Android versions and devices while iPhone enjoys relative security.

The graphic also shows premium devices specifically are vulnerable to their tools, so one cannot argue that the problem is funding or cheap devices getting owned because of dumb changes by the vendor -- premium devices fare not much better. Even Google controlling the hardware and the software of their Pixel line remains vulnerable to data extraction while the latest iPhone versions aren’t.

To me, this sounds like the state of Android physical security might be inferior. Why? What can be done to fix this? Perhaps is it because Android is more popular globally so they get more work targeting Android?

It could also be coincidental that at the time the documents leaked, the iPhone stuff was being finished up and there is actually not that much difference if you have an attacker who has lots of time and money.

EDIT: Removed wrong information. EDIT: Added more material for discussion.

 

After Linux reduced LTS releases from 6 years to 2, Google has committed to supporting its forks for 4 years.

 

AI-generated Summary:

A new leak suggests the Qualcomm Snapdragon 8 Gen 4, featuring an Adreno 830 GPU, will support frame interpolation, allowing games like Genshin Impact to run at 1080p 120 FPS. Frame interpolation, similar to Nvidia's DLSS and AMD's FSR, increases framerates by adding artificial frames but can cause input lag and visual artifacts. This feature might also be available on older Snapdragon models via firmware updates, potentially enabling AAA PC/console games on Android.

My take:

Fascinating that this feature could be supported on mobile, but I'm personally not convinced that there are many mobile gamers pushing the hardware. Most mobile gamers are very casual, and even Apple has trouble getting consumers to take AAA games on mobile seriously.

view more: next ›