Faulty regex and usage of to_s triggers unwanted warning about chef-vault HOT 2 OPEN

This is a major issue. For example, warning is triggered for nested json objects, which are perfectly valid but due to to_s conversion include spaces as field separators. Another big issue is with valid json strings which contain LF, CR etc escape sequences. According to JSON spec, escape sequences are perfectly valid.

perfectly valid json but vault's validator does not validate as to_s

{
   "dummy": {
       "test1": 1,
       "test2": 2
   }
}

to_s converts the value of the key "dummy" to a string like this {:test1=>1, :test2=>2}

Issue with escape sequences

{
"dummy": "aaaa\naaaa\n"
}

Again perfectly valid json with string value, which includes \n escape sequence. Strict RFC 4627 spec based validator validates this example but once again method validate_json triggers warning.

from chef-vault.

@mariastroe @vkarve-chef The biggest issue here is that the warning leaks/displays the value. Can this get fixed ASAP please?

from chef-vault.