> On 9 Dec 2017, at 14:31, Christiaan Hofman <[email protected]> wrote:
>
>
>
>> On 3 Dec 2017, at 13:26, Juergen Fenn <[email protected]> wrote:
>>
>>
>>
>> Am 03.12.17 um 13:02 Uhr schrieb
>> [email protected]:
>>> BTW can either of you find a more detailed error log about this in the
>>> Console app?
>>
>>
>> Indeed, there is a log which says that there was an SSL error. Sparkle
>> was unable to connect to the server in a secure way.
>>
>> Of course, I tried it again after a while, to no avail. OTOH, I don't
>> have this issue with other projects hosted on Sourceforge, e.g., the
>> updater works well with BibDesk.
>>
>> However, thanks for explaining, Christiaan!
>>
>> Best,
>> Jürgen.
>
> BTW, what OS version do you run? I get the impression that older OS versions
> have a bug in their app transport security.
>
> Christiaan
Sorry, I see you already mentioned it was El Capitan. So far, I only get these
reports for that OS version. So I now am quite certain the problem is in El
Capitan. It seems to have a bug in app transport security (blocking of
non-https URLs). Probably related to the fact that this is the OS version that
actually introduced this feature, so bugs weren’t fully ironed out. In that
case I advice you to update your system (you should do so anyway, for security
reasons). The only way we could work around that is to degrade security for
every user, and I really don’t want to do that. Users shouldn’t get less
security because some users don’t update their system.
Christiaan
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Skim-app-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/skim-app-users
