FWIW, I am having the same issue with the update on El Cap. I understand
your reluctance to support less security in order to accommodate bugs, but
I would point out that for a generation of Macbook pro hardware (not sure
of the exact range, but certainly my aluminum MBP is included) El Cap is
the last supported version of OSX so upgrading isn't an option.
Manual download and install is fine for me in that case though! Thanks for
Skim!
Clark
On Sat, Dec 9, 2017 at 5:21 PM, <
[email protected]> wrote:
> Send Skim-app-users mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/skim-app-users
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Skim-app-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Skim-app-users Digest, Vol 124, Issue 1 (Christiaan Hofman)
> 2. Re: Skim-app-users Digest, Vol 124, Issue 1 (Christiaan Hofman)
> 3. Re: Skim-app-users Digest, Vol 124, Issue 1 (Jan David Hauck)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 9 Dec 2017 14:31:54 +0100
> From: Christiaan Hofman <[email protected]>
> To: For general discussion about using Skim
> <[email protected]>
> Subject: Re: [Skim-app-users] Skim-app-users Digest, Vol 124, Issue 1
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=utf-8
>
>
>
> > 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
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 9 Dec 2017 14:45:00 +0100
> From: Christiaan Hofman <[email protected]>
> To: For general discussion about using Skim
> <[email protected]>
> Subject: Re: [Skim-app-users] Skim-app-users Digest, Vol 124, Issue 1
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"
>
>
>
> > 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
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Sat, 9 Dec 2017 12:22:14 -0800
> From: Jan David Hauck <[email protected]>
> To: For general discussion about using Skim
> <[email protected]>
> Subject: Re: [Skim-app-users] Skim-app-users Digest, Vol 124, Issue 1
> Message-ID:
> <CAOrkWyMKg6fkzeMz7K9vvmYB4dHFQsd-k+pA5nuTxRrsh+N2BA@mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I got that error message yesterday on Sierra.
> Tried to reproduce it today after having restarted Skim and it updated
> without problem. Sorry I can't be of more help :/
>
>
> On Sat, Dec 9, 2017 at 5:45 AM, Christiaan Hofman <[email protected]>
> wrote:
>
> >
> >
> > 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
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Skim-app-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/skim-app-users
>
>
> ------------------------------
>
> End of Skim-app-users Digest, Vol 124, Issue 9
> **********************************************
>
------------------------------------------------------------------------------
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
