 |
 |
So, I've now got a successful build. Great! Now I want to strip out all the acceptor stuff (and probably the Shibboleth stuff too, since it's not required) out of the code. The functions that use libradsec definitions in code are peerInitEapChannelBinding and peerProcessChbindResponse. Given this is on the acceptor end, I could do what Luke did with the 'cert_to_byte_array' function (which was #ifdef'd with HAVE_MOONSHOT_GET_IDENTITY). Would that be the appropriate way of dealing with this? However, once I've done this, SSH no longer works, complaining that symbol gss_accept_sec_context cannot be found, and it then defaults back to password authentication. I'd expect us to have whatever is required on a client only? :-/ Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: [log in to unmask] skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.