Closed jennifer-richards closed 6 years ago
Please, don't forget about this one, since you are already working on it.
Thanks
Not forgotten, just pulled away. Hoping to wrap it up today.
That would be superb. Thanks
El 08/08/18 a las 17:07, Jennifer Richards escribió:
Not forgotten, just pulled away. Hoping to wrap it up today.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/painless-security/trust-router/issues/105#issuecomment-411439307, or mute the thread https://github.com/notifications/unsubscribe-auth/AB_G6Lwcgy8LRyiSFajLiyx6eRVty1wsks5uOv6XgaJpZM4VBIic.
-- Alejandro Perez-Mendez Technical Specialist (AAA), Trust & Identity M (+34) 619 333 219 Skype alejandro_perez_mendez 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.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.
This is fixed by #106. It now builds for at least CentOS 7 and Debian Jessie.
I have done basic smoke tests, but have not done much real validation.
Thanks!
A couple of quick questions:
Yes, the v3.4.0 branch has the new code. When happy, that should merge back to master.
The debian-releases/v3.4.0 branch has the latest debian control files. To package, merge the v3.4.0 branch into that and package. After merging v3.4.0 to master, the debian-releases/v3.4.0 branch should merge back to debian.
Thanks! I'm going to test now, although I only have at the moment some smoke tests (build, package, install, create small tr infrastructure, authenticate forcing realm resolution).
The fix to #104 included an attempt to build
trust_router
,tidc
, andtids
against thelibtr_tid
library instead of compiling in their own TID support. This fails to build at the moment due to dependencies between thetr_msg
module and the various messaging families it supports (TID, TRP, and monitoring).The long term fix to this is to disentangle the
tr_msg
module from the protocols that use it. Shorter term, we'll need to buildtrust_router
against its own copy of the TID code instead of usinglibtr_tid
.