New release v2.6.1's signed binaries are not actually strong-named

Aug 19, 2013 at 10:29 PM
Edited Aug 19, 2013 at 10:30 PM
I checked them as of today, and they do not appear to be strong named. Any way we could get this fixed sometime soon please?
Coordinator
Aug 20, 2013 at 7:38 AM
Indeed, I must have had uploaded the unsigned package instead of the signed one by mistake (they were both the same). Fixed.
Marked as answer by cdrnet on 10/3/2013 at 3:31 PM
Aug 20, 2013 at 2:34 PM
Looks good- thanks for the quick fix!