Problem creating new users with MariaDB
Perhaps something different between Maria and MySQL. My experience was with MariaDB.
Problem creating new users with MariaDB
Hate to necropost, but this is the exact issue I just had.
RDM 13.6.7.0.
Fedora Server 28
# mysql --version
mysql Ver 15.1 Distrib 10.2.17-MariaDB, for Linux (x86_64) using readline 5.1
I created a new MariaDB datasource. Connected with the MariaDB root account and created an initial administrator account. The new account did not get created with the "WITH GRANT OPTION" privilege. This caused the "Test Schema" option to fail.
MariaDB [(none)]> SHOW GRANTS FOR 'rdmAdmin'@'%';
+---------------------------------------------------------------------------------------------------------+
| Grants for rdmAdmin@% |
+---------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'rdmAdmin'@'%' IDENTIFIED BY PASSWORD '<snip>' |
+---------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)
After manually updating the rdmAdmin account privileges to include GRANT OPTIONS, the account started working.
The root account does have the correct permissions:
MariaDB [(none)]> SHOW GRANTS FOR 'root'@'%';
+--------------------------------------------------------------------------------------------------------------------------------+
| Grants for root@% |
+--------------------------------------------------------------------------------------------------------------------------------+
| GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY PASSWORD '*478DA7BE4EA792031DF24E0467EEEF1D1488B72D' WITH GRANT OPTION |
+--------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)
Automatic Update Not Updating to Current Version
Thanks for the explanation.
Automatic Update Not Updating to Current Version
Automatic Update is not updating RDM to the latest version. The update, updated to 13.5.8.0 and checking for an update does not offer 13.5.9.0. Is this a bug or is there some kind of delay from release until the client will auto update to the latest?

Support SSH CA Key Signing
Putty supports the signed keys, but doesn't have any of the signing capabilities.
Support SSH CA Key Signing
SSH has a concept of key signing that is similar to x509 (not the same). This capability allow great control of ssh key validity by tying it to a central authentication source.
Signed host key, allows you to validate that the key is trusted without needing to verify the fingerprint.
Signed client key removes the need to maintain authorized_key files.
It would be awesome if RDM had the ability to generate/store the SSH CA key and perform key generation and signing.
This sign provides a better explanation and breakdown of how it works. https://ef.gy/hardening-ssh
SSH Private Key - Show Authorized Key
When using a stored private key, there needs to be a way to easily get the authorized key value. Similar function is available in Keepass2 KeeAgent plugin.
When you open the private key or "personal private key" credential, it should have a field displaying the authorized key with button to copy to clipboard. This could replace the private key view which is very rarely needed. The private key display could be a separate button that shows the raw data in a popup or something.
Further enhancement would be to have a button on ssh and other relevant session entries that allows you to copy the authorized key straight to your clipboard for the selected key.
A step past that, would be implementing "ssh-copy-id" functionality, which SSHes to the host and populates the authorized_key value automatically. This function should also set the proper file permissions. I recognize this function would not work all of the time due to differences in OS environments, but would work more often than not.
SSH Key Agent using stored private keys
Awesome. I can't wait to test it out. :)
AD Integrated - Default to Domain in object selector
Yes, definitely a native windows dialog box. I ask, because I (almost?) always see the location field defaulted to the domain. Suggesting, it is just a property of the form. Thanks. You guys are fantastic at responding to these requests.
AD Integrated - Default to Domain in object selector
http://i.imgur.com/gXz9QqN.png
Domain joined PCs will default to the domain in most cases. To see this behavior:
Computer Management -> Local Users and Groups -> Groups -> <randomGroup> -> Add.
You will see the location defaulted to the domain.
AD Integrated - Default to Domain in object selector
When a system is AD Integrated, the object selector form should default to the domain instead of the host.
eg. Creating a new role. Click the ellipsis button, and the "From this location:" field should be the domain that the system is joined to. Applies to creating a new user as well when the AD Integrated check box is selected.
SMTP Authentication
Updated and verified it is working.
SMTP Authentication
Awesome. Thanks.
SMTP Authentication
Not sure if this is a bug or a feature request but... RDS requires user auth for SMTP. I manage access to this SMTP Relay service by IP and do not have user auth setup currently. Would you please make username/password an optional field in the SMTP configuration?
Encrypted, Authenticated, Dual-stack, Single User Data Source that supports attachments
After a few more hours of futzing with this, I have found 2 more problems.
1. The MySQL/MariaDB doens't even attempt to connect over IPv6. Straight to v4 when dual stacked.
2. More importantly, I can not find any mechanism to tell RDM to use TLS for the connection. Only references to MySQL/MariaDB and SSL are for client authentication. Is that even a function within RDM? MySQL/MariaDB over TLS?
Encrypted, Authenticated, Dual-stack, Single User Data Source that supports attachments
It would be great if there could be some combo of SFTP+SQLLite. If/when I get MySQL/MariaDB/other functional as I want it, I will try to post a howto.
Encrypted, Authenticated, Dual-stack, Single User Data Source that supports attachments
I am looking for a way to accomplish the following with a Data Source
1. Can be accessed on tcp/443 with TLS encryption
2. Works on both IPv4 and IPv6
3. Provides an authentication mechanism
4. Supports attachments
5. Doesn't cost a fortune per year
6. Doesn't depend on 3rd party drive sync. Makes mobile complicated.
*. Bonus of being multi-user and having connection logs.
Going down the list of Data Sources, I am left with very few potentials.
AWS - no attachments
Devolution Server - $500/yr to get attachments.
Dropbox - no attachments
FTP - no attachments
MariaDB/MySQL - doable, but very hackish
Access - lol, no
Azure - Can't change the port (AFAIK)
SQL Server - Expensive to host, but might be doable
Online Drive - no attachments
SFTP - no attachments
SQLLite - not networked, would require Dropbox/Drive/other to share DB around.
Web - Read Only
XML - not networked, would require Dropbox/Drive/other to share DB around (What I am doing currently + Keepass)
MariaDB/MySQL is currently the "best" solution, but it is very hackish to get it dual-stacked, on port 443 and using SSL.
Is there a better solution? I would be happy to pay something like $5/mo for Online Drive if it included attachments.
SSH Key Agent using stored private keys
Today, I use Keepass as my credentials store because of better functionality. One in particular is the combination of Keepass+keeagent which allows me to store my private SSH keys in the vault and then present them to ssh clients via a key agent.
http://lechnology.com/software/keeagent/
In additional to making the keys accessible via standard key agent functionality, it also allows me to create a socket that allows me to use the keys with native Cygwin SSH key agent. The end result is, my private keys are stored securely inside Keepass and presented to any ssh client on my system.
This would also have the added benefit of private keys stored in RDM not being limited to the built in ssh client.
S3 datasource - attachments
> PVM is also but a subset of RDM features.
I was not aware of this. I thought they were separate products that complimented each other.
I am a long time user of RDM+Keepass for storing credentials. I have recently added OSX to my toolbag and I would like to have my connections and credentials shared between Win and OSX. Problem is, OSX doesn't support Keepass that I can tell. This makes my connections in RDM pretty useless. Not to mention the crashing/errors from when I load my connections.xml file from Windows.
I do not have the same level of confidence regarding the security of PVM vs. Keepass for my credentials and would like to continue using KP. However, I don't think I have an alternative solution to storing credentials in RDM/PVM if I want the portability between OSX and Windows.
EDIT:..
However, I store attachments/licenses/etc. in my KP safe which is what led to this question.
Requirements are:
1. Portability between OSX and Windows for both connections and credentials.
2. Ability to store attachments.
3. Ability to easily/automatically synchronize my connections between my hosts.
edited by mrjester on 2/28/2015
Amazon S3 Connection Problems on RDM for Windows
10.1.9.0.
I did try creating it as well.
edited by mrjester on 2/28/2015
Amazon S3 Connection Problems on RDM for Windows
I am getting the same error when setting up a new datasource with RDM.
S3 datasource - attachments
I am a heavy Keepass user and am looking for a better cross-platform (Win+OSX) solution to work with RDM or in place of RDM. PVM seems to be a good potential, but I need the ability to store attachments. Is there a timeline for further support of the features when using S3 datasources?
Feature is missing per: http://help.passwordvaultmanager.com/index.html?datasource_overview.htm
Not keeping window sizing using MainFormMinimal*
Awesome. Thank you.
Not keeping window sizing using MainFormMinimal*
Using the MainFormMinimalHeight and MainFormMinimalWidth config options and only showing the navigation frame, upon restart, the main window doesn't remember its size from when it was last closed.
To reproduce:
Add:
<MainFormMinimalHeight>50</MainFormMinimalHeight>
<MainFormMinimalWidth>50</MainFormMinimalWidth>
Turn off all layout features except navigation and resize the window down to something small.

Restart the application and I get this:

Ideally, it would retain the width that I set it too before I closed it last.
Window Resize
Setting the vertical value did make it stick.