The Bob
@theboberito.bsky.social
Striving to be the strongest and most jacked Mac Admin in all the land.
Seriously though I did 1.0 on Feb 24, 2024...so 18 months later with regular releases I've hit 2.0. It's been awesome to see that people use it and appreciate it. Thank you all for downloading, using, sharing, and submitting issues and feedback.
Makes me feel like a real swift developer.
Makes me feel like a real swift developer.
October 28, 2025 at 2:24 PM
Seriously though I did 1.0 on Feb 24, 2024...so 18 months later with regular releases I've hit 2.0. It's been awesome to see that people use it and appreciate it. Thank you all for downloading, using, sharing, and submitting issues and feedback.
Makes me feel like a real swift developer.
Makes me feel like a real swift developer.
If it compiles, it ships!
October 24, 2025 at 9:32 PM
If it compiles, it ships!
I’m not sure if there’s a vulnerability there or not with leaked information. I’m not even sure how to hunt or look for that.
Is a developer support ticket the best way to report this? Or the Blackhole of Apple feedback?
Is a developer support ticket the best way to report this? Or the Blackhole of Apple feedback?
October 20, 2025 at 11:33 PM
I’m not sure if there’s a vulnerability there or not with leaked information. I’m not even sure how to hunt or look for that.
Is a developer support ticket the best way to report this? Or the Blackhole of Apple feedback?
Is a developer support ticket the best way to report this? Or the Blackhole of Apple feedback?
Then with SIP disabled I could connect Instruments to it. Lo and behold, memory leak when viewing a certificate!
I imagine it’s using the same class and not some proprietary private API thing.
I also imagine it’s ancient code that hasn’t been updated in forever.
I imagine it’s using the same class and not some proprietary private API thing.
I also imagine it’s ancient code that hasn’t been updated in forever.
October 20, 2025 at 11:32 PM
Then with SIP disabled I could connect Instruments to it. Lo and behold, memory leak when viewing a certificate!
I imagine it’s using the same class and not some proprietary private API thing.
I also imagine it’s ancient code that hasn’t been updated in forever.
I imagine it’s using the same class and not some proprietary private API thing.
I also imagine it’s ancient code that hasn’t been updated in forever.
Whenever I create an instance of an SFCertificateView and set setDisplayDetails(true) it causes a leak. I’ve talked with some people, consulted all the AI gods, tried a bunch and always happens.
Since i believe Keychain Access probably uses the same thing I disabled SIP.
Since i believe Keychain Access probably uses the same thing I disabled SIP.
October 20, 2025 at 11:30 PM
Whenever I create an instance of an SFCertificateView and set setDisplayDetails(true) it causes a leak. I’ve talked with some people, consulted all the AI gods, tried a bunch and always happens.
Since i believe Keychain Access probably uses the same thing I disabled SIP.
Since i believe Keychain Access probably uses the same thing I disabled SIP.
Server side swift is definitely an interesting thing to me. I wonder if I could somehow build some server to build pieces from the macOS security compliance project. Like an api if you will.
October 5, 2025 at 1:39 AM
Server side swift is definitely an interesting thing to me. I wonder if I could somehow build some server to build pieces from the macOS security compliance project. Like an api if you will.