You did not specify which OS you are using. ![]() I think it did not like our second use case because it lacked a number.īut, if we also up the length significantly (while trimming problems) the odds go up significantly that what we are left with will be something its happy with. We are still left with the problem of generated value lacking certain characters. We will shamelessly steal your little trick to trim known problematic characters. These days I exclude a couple of other characters as well. Runmqakm -random -create -length 125 -strong | tr -d "'" | tr -d ' | cut -c 2-65 > key.passwd The command I used during the residency when writing the book was There's some sample (linux shell) code for this in the Secure Messaging Scenarios using WebSphere MQ IBM Redbook publication in section 8.11. Then I truncate the result down to 60 characters or so. When using it to generate something I'm going to use as a passphrase, I always generate something quite large (120 bytes or so) and then filter out the characters that tend to cause problems to a shell and a few others). I always considered that the function was generating random bytes, rather than actual passphrases or passwords. >runmqakm -keydb -create -db mykeystore.kdb -pw "hidden" -type cms -stash -fips -strong >runmqakm -keydb -create -db mykeystore.kdb -pw "U$uK^_Ll,vpi)c" -type cms -stash -fips -strong ![]() usr/bin/runmqakm: eval: line 112: syntax error: unexpected end of file usr/bin/runmqakm: eval: line 111: unexpected EOF while looking for matching `'' >runmqakm -keydb -create -db mykeystore.kdb -pw " z#HW)j+(RAb/'c" -type cms -stash -fips -strong >runmqakm -random -create -length 14 -strong -fips Would it be considered a defect that runmqakm's password generator doesn't consistently make passwords that runmqakm itself is happy with?
0 Comments
Leave a Reply. |