From: Bastien <bzg@gnu.org>
To: Richard Stallman <rms@gnu.org>
Cc: kfogel@red-bean.com, vibhavp@gmail.com, monnier@iro.umontreal.ca,
mccracken.joel@gmail.com, emacs-devel@gnu.org
Subject: Re: twitter.el, anyone?
Date: Tue, 21 Jan 2014 16:26:23 +0100 [thread overview]
Message-ID: <87lhy9gxuo.fsf@bzg.ath.cx> (raw)
In-Reply-To: <E1W5cXM-0000ji-Hz@fencepost.gnu.org> (Richard Stallman's message of "Tue, 21 Jan 2014 09:42:44 -0500")
twittering-mode relies on data called Root Certificates.
Here is an example of a Root Certificate:
-----BEGIN CERTIFICATE-----
MIICPTCCAaYCEQDNun9W8N/kvFT+IqyzcqpVMA0GCSqGSIb3DQEBAgUAMF8xCzAJ
BgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xh
c3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw05
NjAxMjkwMDAwMDBaFw0yODA4MDEyMzU5NTlaMF8xCzAJBgNVBAYTAlVTMRcwFQYD
VQQKEw5WZXJpU2lnbiwgSW5jLjE3MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJp
bWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTCBnzANBgkqhkiG9w0BAQEFAAOB
jQAwgYkCgYEA5Rm/baNWYS2ZSHH2Z965jeu3noaACpEO+jglr0aIguVzqKCbJF0N
H8xlbgyw0FaEGIeaBpsQoXPftFg5a27B9hXVqKg/qhIGjTGsf7A01480Z4gJzRQR
4k5FVmkfeAKA2txHkSm7NsljXMXg1y2He6G3MrB7MLoqLzGq7qNn2tsCAwEAATAN
BgkqhkiG9w0BAQIFAAOBgQBMP7iLxmjf7kMzDl3ppssHhE16M/+SG/Q2rdiVIjZo
EWx8QszznC7EBz8UsA9P/5CSdvnivErpj82ggAr3xSnxgiJduLHdgSOjeyUVRjB5
FvjqBUuUfx3CHMjjt/QQQDwTw18fU+hI5Ia0e6E1sHslurjTjqs/OJ0ANACY89Fx
lA==
-----END CERTIFICATE-----
These certificates are provided by Symantec.
When redistributing them with their software, developers have to agree
with the Root Certificate License Agreement that can be found here:
http://www.symantec.com/content/en/us/about/media/repository/root-certificate-license-agreement.pdf
Developers don't need to sign the agreement, they implicitely accept
it by using and redistributing the certificates.
My reading of the license agreement above is that using Symantec
certificates in a software creates a lot of constraints for the
developers and that these constraints are not compatible with using
them in a free software -- but I may be wrong and I will let someone
else double-check.
In the meantime, I told the twittering-mode maintainers about this
problem and they will check themselves, hopefully coming up with
other certificates.
--
Bastien
next prev parent reply other threads:[~2014-01-21 15:26 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 4:04 twitter.el, anyone? Richard Stallman
2014-01-15 4:24 ` Joel Mccracken
2014-01-15 7:08 ` Karl Fogel
2014-01-15 14:53 ` Stefan Monnier
2014-01-15 16:31 ` Bastien
2014-01-16 17:56 ` Richard Stallman
2014-01-16 18:13 ` Vibhav Pant
2014-01-16 21:16 ` Joel Mccracken
2014-01-17 1:39 ` Stephen J. Turnbull
2014-01-17 5:48 ` chad
2014-01-17 14:10 ` Richard Stallman
2014-01-17 14:34 ` Bastien
2014-01-18 12:33 ` Richard Stallman
2014-01-18 13:17 ` Vibhav Pant
2014-01-18 13:22 ` Vibhav Pant
2014-01-19 12:12 ` Richard Stallman
2014-01-19 13:25 ` Vibhav Pant
2014-01-20 9:14 ` Richard Stallman
2014-01-19 15:26 ` Bastien
2014-01-19 17:54 ` Achim Gratz
2014-01-20 9:32 ` Bastien
2014-01-19 20:29 ` Stefan Monnier
2014-01-20 9:46 ` Bastien
2014-01-20 19:22 ` Richard Stallman
2014-01-20 20:40 ` Bastien
2014-01-21 14:42 ` Richard Stallman
2014-01-21 15:10 ` Bastien
2014-01-22 15:31 ` Richard Stallman
2014-01-23 8:20 ` Bastien
2014-01-23 17:18 ` Richard Stallman
2014-01-20 19:20 ` Richard Stallman
2014-01-20 19:22 ` Richard Stallman
2014-01-20 20:40 ` Bastien
2014-01-21 14:42 ` Richard Stallman
2014-01-21 15:26 ` Bastien [this message]
2014-01-23 10:55 ` Richard Stallman
2014-01-23 11:46 ` Bastien
2014-01-15 7:08 ` David Kastrup
2014-01-15 7:42 ` Vibhav Pant
2014-01-15 8:53 ` chad
2014-01-16 17:53 ` Richard Stallman
2014-01-16 18:59 ` David Kastrup
2014-01-16 21:38 ` Sebastien Vauban
2014-01-17 1:14 ` Vibhav Pant
2014-03-07 10:59 ` Steinar Bang
2014-03-07 12:11 ` Matt Ford
2014-03-07 13:35 ` Tassilo Horn
2014-03-08 9:45 ` Grim Schjetne
2014-03-08 15:11 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhy9gxuo.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=mccracken.joel@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=vibhavp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.