This component uses a weak password derivation function - it simply shuffles the activation code using a static pattern so anyone with your activation code can derive the master AES key. Since the activation code is also in the database, an attacker who compromises the database can trivially extract the activation code, shuffle it, and decrypt all passwords saved using this app.

I don't want to sound overly critical because this is a hard problem to solve and I haven't found a better solution myself, but I believe claiming this app has an "encryption" feature is misleading, because without a secure password derivation function, it is essentially just obfuscation.

I love this application. I was trying to build something like this for sometime but you also tought about logging and whitelisting, which might come in handy. The one thing that I would like to have different is way the password is used inside the code because, right now I need to know what code relates to what password and as developer I think this is a problem and I don't have solution for this. A good way would be to have a static reference, but because creating records in static entities can only happen in design time, this lives me with another problem :)
Despite this, great app.

This is a great tool and an essential component for any Factory. thx Nuno!