Comment 13 for bug 1561533

Hi Margaret,

the SIGSEGV is still there. I have easily reproduced it on a newly created Centos 7 LXC container.
The problem is that I don't see an easy way of getting rid of the <optimized out> variables.
If you can guide me through the process, I'd be more than pleased to help you (I will keep the set up for some weeks now).

Nevertheless, let me describe the steps to simulate this scenario using LXC. Perhaps the problem is on how I'm building and installing the SW:
1. Create a new LXC container: Centos 7 AMD64
2. yum install epel-release wget
3. cd /etc/yum.repos.d
4. wget http://download.opensuse.org/repositories/security://shibboleth/CentOS_7/security:shibboleth.repo
5.yum install nano automake autoconf libtool libconfuse-devel python fakeroot krb5-devel libevent-devel wget git boost-devel libconfuse-devel gcc-c++ bash-completion log4cpp-devel xerces-c-devel openssl-devel libcurl-devel gtk2-devel dbus-devel glib-devel libgee-devel dbus-glib-devel shared-mime-info gnome-keyring-devel libgnome-keyring-devel desktop-file-utils make libxml-security-c-devel gettext-devel libgee06-devel vala libsaml-devel opensaml-schemas opensaml-bin shibboleth-devel shibboleth-resolver-devel
6. git clone --recursive http://www.project-moonshot.org/git/moonshot.git
7. edit source_packages and enable only: libradsec jansson ui moonshot
7. Execute the builder (no additional options).
8. ln -s /usr/local/moonhost/lib/gss /usr/lib64
9. Copy moonshot/mech_eap/mech into /etc/gss/mech.d/moonshot.conf
10. Create a /usr/local/moonshot/etc/radsec.conf file (mine uses UDP instead of RADSEC for convenience, I don't think it's relevant thought).
11. Execute gss-server test@test and try to authenticate using a gss-client. At the end of the authentication process, gss-server MUST fail.

Hope this helps!