Uh, well my response was sarcasm. I don’t see any value in encoding it twice. I do see a small negative effect though in the increased number of bytes. But my point is that somebody who has the experience to look at a string and determine that it’s probably base 64, will still have that ability when looking at the decoded string.
You’d be better off encoding in something less recognizable, like base 32. It’d be slightly more efficient on storage, is less recognizable, and fewer libraries have functions to deal with it.
Or just not bother.
2 Likes
He could double-encode it in ROT-13. 
2 Likes
Oh well.
Sarcasm. Ok.
He didn’t say how secure he wanted it, where he was putting it etc.
He said he wanted something simple to implement.
2 more lines of code and he could have had something impossible to brute force, just like the old book codes used to be.
He’s got a full blown encryption solution now, so that’s good. I shouldn’t have said anything.
For the original problem OP is having,
Does anyone know of a way to access Keychain / Passwords on iOS?
@Christian_Schmitz 's documentation says his plugin does not support iOS.