If I use an unencrypted password that starts with an equal sign with the password option in the userlist, instead of the insecure-password option then HAProxy segfaults when I try to log in as the user with the badly configured password. I realize that I should not be using an unencrypted password in this case, but it's not good that it causes a segfault.
This line in the userlist will cause the segfault when you try to view stats as the user test: user test password =testing The segfault error from messages is: Jun 25 21:33:41 dev-tsl-haproxy-001 kernel: [ 4147.107578] haproxy[6780]: segfault at 0 ip 00007f6ae5fcfef6 sp 00007ffc0e6a04d8 error 4 in libc-2.17.so[7f6ae5e9e000+1b6000] I'm running HAProxy version 1.5.2 in the AWS OpsWorks HAProxy layer on Amazon Linux 2015.03 Sean
