I’ve been working around the clock for almost 2 weeks, pouring my heart and soul into an App, and I’m getting to a point where security over the code base is becoming more and more valuable.
I want to avoid going into that part of the process completely blind…
Are there any ‘best methods’ established for adding a security layer to your App that Codex works well with?
Should I attempt to have Codex invent new ones?
What are your thoughts?
Did you ask ChatGPT about your concerns?
Maybe he can point you to best practices in that regard?
Besides the obvious “asking codex for checking security breaches”, I believe there are a few security related curated skills that you can use in codex by calling $skill-installer
Yeah, I got the full list of practices ^.^ But they’re all merely annoyance layers without an actual server out there in the cloud.
I have ideas that I’m pretty sure just amount to nothing more than levels of annoyance…
Maybe there’s someone smarter than me…
Maybe we’re really kinda screwed, and machine binding is the best we’ve got with offline Apps.
Maybe there’s something to be said about multi-keys and false unlocks, but that still doesn’t forbid file patching…
I guess I didn’t mention I am familiar with the standards already - I was just kind of hoping that I was being blind and old fuddy duddy about the process….
I will check those skills.md out today, thank you @aprendendo.next !
Ultimately, it’s a non-issue if I bring the product to market, but we’re not quite at that point with what I’m doing yet.