opensesame VS PermissionsSwiftUI

Samy Kumar did a project about 10 years back, where he worked out how to brute force a 12 bit garage door code in under 10 seconds, using a childs toy: http://samy.pl/opensesame/

My garage door opener uses a 12 but dip switch config (and my last place used an 8 dip switch config, and I'm pretty sure still does).

Re reading that OpenSesame post was fun. It reminded me of a few names I need to go find out what they're up to these days (Travis Goodspeed and Michael Ossmann are names I remember seeing doing/writing-up some really cool stuff), and that the Mattel IM-ME toy he was using uses that same CC1110 "sub gHz"

At this point let's just cite his site http://samy.pl/opensesame/

Yes, there are only 512 combinations for a 9 bit receiver like this. More switches adds more combinations, but all of these style openers are susceptible to a "replay attack" where you record the signal from the opener and play it back later. They are also at risk of more sophisticated brute force attacks (https://samy.pl/opensesame/) Modern openers use a "rolling code" system that is safer, but the truth of the matter is that it is very very rare for anyone to exploit these old openers.

Functionally anything that can be attacked by OpenSesame can be programmed in, but that list is pretty small these days.

Perhaps someone could create a flipper compatible file using this existing opensesame source code

Hey all! Well, my flipper has finally arrived, and I'm delighted. I'm interested in exploring some minor development on it, and in particular was looking at trying to get samyk's opensesame attack working. As the code is all there on github, and his device used the same RF chipset. I presume it should be a relatively simple matter to get it going on the flipper, but not quite sure how to start with it, as I guess the dev docs are still only in Russian...

I think it depends on the overall UI/UX design. But I plan on adding a pop up alert style for the 0.0.1 release milestone so developers can have the choice to present it right before the permission is actually needed.

The video demonstrates PermissionsSwiftUI, a SwiftUI package to beautifully display and handle permissions.

Obviously, you should not do this in real life app. The "pro gamer move" is kind of a meme which points out how unexpected it is to ask for every single permission in iOS. And here I used my PermissionsSwiftUI library to easily present all the iOS permissions. My library also allows you to customize the description text on the screen, developers should also have the description in their info.plist. Reference SPPermissions, it does the same thing, and it has 4000 stars

Lol, this comment is getting a lot of upvotes. Obviously, you should not do this in real life app. The "pro gamer move" is kind of a meme which points out how unexpected it is to ask for every single permission in iOS. And here I used my PermissionsSwiftUI library to easily present all the iOS permissions. My library also allows you to customize the description text on the screen, developers should also have description in their info.plist.

PermissionsSwiftUI: A SwiftUI package to beautifully display and handle permissions.

Sure! I'm still a student, but I am very experienced in Swift programming and SwiftUI. I recently made a Swift Package - PermissionsSwiftUI and maybe I can use 5-10 minutes to walk through how I made it, the interesting challenges, and my cool SwiftUI tips and tricks.