25 янв. 2015 г. 1:29 пользователь "Vadim Zhukov" <persg...@gmail.com>
написал:
>
> 25 янв. 2015 г. 1:04 пользователь "Adam Wolk" <adam.w...@koparo.com>
написал:
>
> >
> > On Sat, Jan 24, 2015, at 10:52 PM, Vadim Zhukov wrote:
> > > 2015-01-24 21:02 GMT+03:00 Adam Wolk <adam.w...@koparo.com>:
> > > > On Thu, Jan 22, 2015, at 02:29 AM, Brian Callahan wrote:
> > > >> Hi ports --
> > > >>
> > > >> Attached is a new port, www/quiterss. QuiteRSS is a free Qt-based
> > > >> Atom/RSS news reader (think: the Qt version of www/liferea).
> > > >>
> > > >> pkg/DESCR:
> > > >> QuiteRSS is a open-source cross-platform RSS/Atom news feeds
reader. It
> > > >> is designed to be fast and comfortable for the user. It includes an
> > > >> embedded webkit browser, adblocking, user filters, and proxy
> > > >> configuration, among many other features.
> > > >>
> > > >> ---
> > > >>
> > > >> This works well for me on amd64. Note the patch. I don't know if
this is
> > > >> an issue with QuiteRSS, Qt4, Fluxbox, or something else. Would
> > > >> appreciate testing on the big DEs if possible. With the patch, I
can get
> > > >> QuiteRSS to show and hide itself from the little tray icon.
Without it,
> > > >> once I hide QuiteRSS it is unable to reshow itself.
> > > >>
> > > >> OK?
> > > >>
> > > >> ~Brian
> > > >>
> > > >> Email had 1 attachment:
> > > >> + quiterss.tgz
> > > >>   2k (application/x-gtar)
> > > >
> > > > Hi Brian,
> > > >
> > > > The port builds and installs fine on OpenBSD i386 snapshot from Jan
22.
> > > > Upon startup I am hitting a 'SSL Certificate Error!' for '
openstat.net'
> > > > with the following details:
> > > >  - Error: The issuer certificate of a locally looked up certificate
> > > >  could not be found
> > > >  - Error: The root CA certificate is not trusted for this purpose
> > > >  - Error: No certificates could be verified
> > > > I told it I don't want it to trust the cert and moved on.
> > >
> > > This was a Qt problem rather, already fixed in CVS: the same issue was
> > > with Qt4 some time ago - it didn't try to lookup SSL certificates in
> > > /etc/ssl/.
> > >
> > > Regarding port itself, I'll take a look, likely tomorrow. Feel free to
> > > CC me for any Qt-related ports, to make sure I don't miss 'em on
> > > ports@.
> >
> > Hi @zhuk,
> >
> > Interesting that you mention that it's a fixed issue in Qt.
> > this is a qt4 port and I'm hitting this pretty consistently but only
> > for the feed bundled with the app, others load fine.
> >
> > MODULES =       x11/qt4
> >
> > Was this issue fixed recently in qt4? I'm seeing this with
> > the following package: qt4-4.8.6p0 (installed)
> >
> > Here is the dynamic section from the app binary obtained from objdump
> > -p:
> >
> > Dynamic Section:
> >   NEEDED      libsqlite3.so.28.0
> >   NEEDED      libQtWebKit.so.4.0
> >   NEEDED      libphonon.so.4.1
> >   NEEDED      libQtDBus.so.2.0
> >   NEEDED      libQtSql.so.8.0
> >   NEEDED      libQtXml.so.8.0
> >   NEEDED      libQtGui.so.10.1
> >   NEEDED      libfreetype.so.23.0
> >   NEEDED      libSM.so.9.0
> >   NEEDED      libICE.so.10.0
> >   NEEDED      libXi.so.12.1
> >   NEEDED      libXrender.so.6.0
> >   NEEDED      libXinerama.so.6.0
> >   NEEDED      libfontconfig.so.9.1
> >   NEEDED      libXext.so.13.0
> >   NEEDED      libX11.so.16.0
> >   NEEDED      libQtNetwork.so.10.0
> >   NEEDED      libQtCore.so.9.0
> >   NEEDED      libstdc++.so.57.0
> >   NEEDED      libm.so.9.0
> >   NEEDED      libpthread.so.18.1
> >   NEEDED      libc.so.78.1
>
> Yes, it was fixed in Qt4 a long time ago. I discovered the problem while
working on KDE4 port: Konqueror and KMail were constantly whining about
untrusted certificates, and after applying the fix they became happy.
>
> Sorry, I missed it that this is a Qt4 app - I saw the "Qt" and added "5"
by inertion. Then it's strange, there should be no whining from Qt, unless
the certificate is really bad. I'll check things closely a bit later. Maybe
SSL certificate search path is overwritten somewhere inside the QuiteRSS?

Yes, that's upstream problem. I found a discussion (in Russian), upstream
still tries to fix issue.

I see they have SSLv3/TLSv1 somewhere in certificate chain, just run
"openssl s_client -connect quiterss.org:443".

--
Vadim Zhukov

Reply via email to