[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SSL/TLS client?
On Thu, Aug 19, 1999 at 12:22:05PM +0400, Eugene Crosser wrote:
> On 19-Aug-99 at 01:56, Ken Lalonde (email@example.com) wrote:
> > One fruitful way to do this would be to change zmailer
> > to use AT&T's sfio library instead of stdio.
> > Sfio supports "disciplines", which should make SSL integration easy,
> > and has other benefits, in particular speed and portability.
> > It would also help eliminate some old less-than-elegant code,
> > such as the "sio" stuff in the router.
> > http://www.research.att.com/sw/tools/sfio/
> I am not a layer but "Permission to use, copy, modify, and distribute
> this software for any purpose without fee is hereby granted" makes
> me think that if you include sfio source then the resulting package
> *may* be illegal to distribute e.g. on a cdrom if it's cost is non-zero.
Phong Vo <firstname.lastname@example.org> resolved it this way when I asked:
> That said, what comes up as heading for the actual download page did
> scare me somewhat:
> Non-Exclusive Limited-Use Software
> Eh ? What that "Limited-Use" means here ?
This is probably just an artifact of the software distribution area that
we maintain for a whole bunch of different tools. Sfio is completely free.
If you include its source in your distribution, then you must include the
included copyright notice. That's all.
> A happy interpretation for "Limited-Use" is much same as "No Warranty",
> but I am not a lawyer..
Me neither. But is true that Sfio offers no warranty. You use it
at your own risk.
Ok, I will start engineering study ( = open the package and read documents )
about how to use it, and how large an impact it will be when linked into
programs. (In terms of binary footprint.)
Indeed ATT Research does have a habit of publishing some of its products
in BSD-like licenses where credit is called for, but no other strings are
Ken, thanks for the pointer!
/Matti Aarnio <email@example.com>