From: Andrew Lunn <andrew.lunn@ascom.ch>
To: "kjell@techtribe.se" <kjell@techtribe.se>
Cc: Peter Vandenabeele <peter.vandenabeele@mind.be>,
ecos-discuss <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Goahead Web Server on i386
Date: Mon, 06 Jan 2003 09:56:00 -0000 [thread overview]
Message-ID: <20030106095605.GK1386@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <3E195122.5060103@techtribe.se>
> As for what goes for the SSL stuff; I'm aware that there are possible
> patent and licensing issues for some (many?) of the algorithms provided
> in the OpenSSL package. Since we have only wrapped this up for internal
> try-outs, we haven't spent much effort into checking those licensing
> details in any greater depth.
>
> But since the port turned out to be pretty straightforward and the SSL
> proved to be working quite well, maybe someone interested in using the
> SSL would be willing to dig deeper into its licensing and patent details?
Is this my OpenSSL port?
If so, i did a tiny amount if research in this area. I basically read
that is says in the OpenSSL distribution about which parts of it are
covered by patents and licenses. I added CDL which made these parts
optionally compilable and by default disabled.
This is a start, but the standard IANAL disclaimer applies and you
should check for yourself.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2003-01-06 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 23:10 Fred Woolsey
2003-01-05 19:21 ` kjell
2003-01-05 21:28 ` Peter Vandenabeele
2003-01-06 9:49 ` kjell
2003-01-06 9:56 ` Andrew Lunn [this message]
2003-01-06 10:23 ` kjell
2003-01-06 10:30 ` Andrew Lunn
2003-01-06 10:24 ` Peter Vandenabeele
2003-01-07 21:16 ` Jonathan Larmour
2003-01-07 21:34 ` Patrick Doyle
2003-01-07 21:58 ` Gary Thomas
2003-01-06 15:29 ` Grant Edwards
2003-01-07 0:35 ` [ECOS] C Linkage for C++ Files Fred Woolsey
2003-01-07 1:11 ` Greg Lanthier
2003-01-07 1:19 ` Fred Woolsey
2003-01-07 4:27 ` sai jayram
2003-01-07 6:53 ` Fred Woolsey
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=20030106095605.GK1386@biferten.ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=ecos-discuss@sources.redhat.com \
--cc=kjell@techtribe.se \
--cc=peter.vandenabeele@mind.be \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).