Security Concerns: You can break Credentials used to start RDM easily!
Thanks for your reply. I bet there are ways to secure the data, but when it is that hard or unintuitive for me to do so and also so easy to break trough the protection I assumed was save, then this software is just not for me or our company. Also I think you have lots of users who did the same as me to protect their data, thinking their data is secured when it's just not.
I would wish for future users to not get tricked into thinking their data is secured by using the easy accessable password settings. Any password should be set to the data source itself, not any config-file that plays gate-keeper.
I wish you guys best luck and a nice day.
Security Concerns: You can break Credentials used to start RDM easily!
Please try it: Create a new datasource using SQLite, "encrypt" it with a password, close RDM, delete config, restart RDM. You will have your encrypted data source just opened for you.
At this point, I've lost trust.
Security Concerns: You can break Credentials used to start RDM easily!
It's not that deleting the config file doesn't protect my data. It's that deleting the config makes it, that any protection I configured is worthless..
The credentials do not encrypt ANYTHING, they are just a little: "if password is good then let user in." Also: "if I dont know about a password I let any user in!" That's not acceptable at all.
My colleagues just tested a few things with a local database: They don't get encrypted at all! You delete the config.. you get access.
Even when you protect your SQLite database with 2 factors: After deleting the config you just ignore the dialog asking for a new data source and voila... you have access to the database which was used before.
We were not able to secure the local data source at all. We used credentals both for A: starting RDM and B: securing the SQLite DB.
Deleting the config file gives you full access to anything!
We lost trust in this software completely.. it's not that hard to encrypt a database or credentials.
I liked your software and tested it some time for our company, but I am sorry to say.. RDM is banned for now.
Security Concerns: You can break Credentials used to start RDM easily!
Situation:
I work on a VM in our local domain.
I use RDM at different machines.
I save the Datasource in your cloud.
I use a Yubi-key to protect my datasource.
Problem:
Because of problems, I removed RDM to reinstall it.. It didn't delete the *.cfg so I deleted it by hand.
The cfg file includes the use of the Yubi-key.
When I restartet RDM without the cfg file, it just connected to my online datasource WITHOUT asking for ANY credentials.
I didn't even need to give the location to my datasource!
So EVERYONE in my domain who knows this bug can use all my credentials!
Why isn't the datasource better protected? I was flabbergasted when seeing how friggn easily you can break security while using this product!
So how can I make sure, that my datasource is protected? The way it works now, I can't use RDM anymore!
Sync settings like otp and yubikey credentials between different clients?
Thanks for clarification. It would be very nice to have the option to just sync the cfg file when the data sources are synced. But it is what it is and I'm grateful to have such a nice tool for free. Have a nice day. :)
Sync settings like otp and yubikey credentials between different clients?
Hi, I use RDM free on different clients and would like to know if it is possible to sync not only the datasource but also all of the settings between them without copying files manually.
Especially the login credentials to RDM like Ubikey and OTP.
Thanks,
Avialle