[MXS-654] Add test that verifies that maxpasswd does not output garbage. Created: 2016-03-31  Updated: 2016-03-31  Resolved: 2016-03-31

Status: Closed
Project: MariaDB MaxScale
Component/s: test
Affects Version/s: None
Fix Version/s: 2.0.0

Type: Task Priority: Major
Reporter: Johan Wikman Assignee: Johan Wikman
Resolution: Done Votes: 0
Labels: None

Issue Links:
Relates
relates to MXS-653 maxpasswd writes notice message to st... Closed

 Description   

At least on 1.4.1, masspasswd outputs additinal information in addition to the key:

  1. maxpasswd /var/lib/maxscale/data/ mypassword
    6E37E9B0CA3BF6020A3DBCD0DE113546
    2016-03-31 17:03:23 notice : Using encrypted passwords. Encryption key: '/var/lib/maxscale/data/.secrets'.

And everything goes to stdout. That makes it difficult to use maxpasswd in scripts.

Add test-case that verifies that maxpasswd outputs the key and the key alone.

 Comments   
Comment by Johan Wikman [ 2016-03-31 ]

Commit 30d981c87cc2208b820265f9ea06a87c0b7540e3 adds a test to the core test-suite that tests that maxpasswd only outputs as many characters as the key contains.

Thus, random logging to stdout should be caught.

Generated at Thu Feb 08 04:00:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.