MitchellThomas wrote: > Thank you for that fix! It works like a charm. > > So I have two questions: > > > - I would like to pay back the author of the fix somehow... it > wouldn't be much, say the value of a lunch... how can I do that? - Being a software developer, I would love to know some of the > details of the issue/fix. Is there a way I can explore that, > perhaps a github commit or something similar? - > > >
Hi there You are welcome. And thanks for the offer, that is very kind of you, but really not necessary. The issue was the new certificate Rhapsody is using. Each field in a certificate has a type (i.e. plain ASCII string, UTF-8, etc.). In the past the field holding Rhapsody's domain name was marked as plain ASCII string but in the current certificate that changed to UTF-8 (although the content is still a plain ASCII string). The open source library version we were using to verify the certificate did not support UTF-8 fields and therefore the certificate check and Rhapsody playback failed. Switching to a newer version of axTLS fixed the issue. Cheers Felix Programming is the art of cleverly arranging bits and bytes. - (c) Felix Mueller ------------------------------------------------------------------------ fcm4711's Profile: http://forums.slimdevices.com/member.php?userid=42 View this thread: http://forums.slimdevices.com/showthread.php?t=100830 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
