Pinned Tweet
I have just released my first open source project – mach-o files obfuscator written in pure Swift: github.com/kam800/MachObfusc… ✈️
It is language agnostic – doesn't care if app is written in Swift or Obj-C 😎
#obfuscator #security #ios #macho #dyld #swiftlang
0xK4M1L 0xB0RZYM retweeted
Supper happy to upload talk from @kam800 he made for @MobileWarsaw #90 edition
I really love how much Kamil cares about good story in his presentations making complex topics a beautiful and funny journey for the viewers.
Check it out! #iOS #Swift
youtu.be/ralM5TES9Cw?si=yo2L…
0xK4M1L 0xB0RZYM retweeted
A teraz na scenie @kam800 hackuje iOS za pomocą ATARI
0xK4M1L 0xB0RZYM retweeted
iOS Code Review - Issue #57 is out 💌☀️🚀
It features highlights from @chriseidhof @peterfriese @mahyarm8 @kam800 @hybridcattt @NSSpain ✨ -
And thank you @Bitrise for support again ❤️
ioscodereview.com/issues/57/ #SwiftLang #iOSDev
@dgregor79 I have an unexpected pointer in the middle of a swift enum type metadata. A value witness table pointer comes first, then the unexpected pointer, then a kind, finally a nominal type descriptor. Should this happen at all? As far as I know kind should be right after VWT.
I will bury this iPod Touch 4 as a time capsule, so future generations could try to unlock it. (The message says “iPod is disabled, try again in 26 milion minutes”)
0xK4M1L 0xB0RZYM retweeted
Za tydzień w czwartek (17.04) kolejny Allegro Tech Live, tym razem z tematem🔥iOS pod maską🔥
Będziecie mogli usłyszeć @adam_grz @kam800 @fabian_grzes @macpiotrowski89
👉👉meetup.com/pl-PL/allegrotech…
Liczę, że tego nie przegapicie drodzy #iOS Developerzy! 😉
#allegrotech
UPDATE: This setting could cause crashes when used in a SwiftUI app. I stopped using it in my apps. Also mind that this could change behavior or reflection-dependent stuff (e.g. type string interpolation).
0xK4M1L 0xB0RZYM retweeted
Please drop me a line if you missed the chance to ask a question during the talks!
Also if you want to learn more about mobile security after #mDevCamp here are the talks I've mentioned in the second part of my deep dive.
All credits to @kam800, @vixentael, and @kevcody 🤘













