Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8623
| From | Michael Fladischer <michael@fladi.at> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Bug#828940: ITP: python-dropbox -- Official Dropbox API Client |
| Date | 2016-06-29 10:50 +0200 |
| Message-ID | <rPjm1-1VD-9@gated-at.bofh.it> (permalink) |
| References | <rPjm1-1VD-11@gated-at.bofh.it> |
| Organization | Fladi.at |
[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
Back to linux.debian.maint.python | Previous | Next | Find similar | Unroll thread
Re: Bug#828940: ITP: python-dropbox -- Official Dropbox API Client Michael Fladischer <michael@fladi.at> - 2016-06-29 10:50 +0200
csiph-web