Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #8623 > unrolled thread

Re: Bug#828940: ITP: python-dropbox -- Official Dropbox API Client

Started byMichael Fladischer <michael@fladi.at>
First post2016-06-29 10:50 +0200
Last post2016-06-29 10:50 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Bug#828940: ITP: python-dropbox -- Official Dropbox API Client Michael Fladischer <michael@fladi.at> - 2016-06-29 10:50 +0200

#8623 — Re: Bug#828940: ITP: python-dropbox -- Official Dropbox API Client

FromMichael Fladischer <michael@fladi.at>
Date2016-06-29 10:50 +0200
SubjectRe: Bug#828940: ITP: python-dropbox -- Official Dropbox API Client
Message-ID<rPjm1-1VD-9@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Hi folks,

I'm not sure how to handle the trusted certificates[0] included in
python-dropbox.

They all are valid until at least 2020 but I don't want to leave them
like this in a stable release.

Would it make sense to patch the source to take those certificates from
ca-certificates. Or should I consider removing handling of separate
trusted certificates and let the whole of ca-certificates be trusted?

[0]
https://github.com/dropbox/dropbox-sdk-python/blob/master/dropbox/trusted-certs.crt

Cheers,
-- 
Michael Fladischer
Fladi.at

[toc] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web