Date: Fri, 10 Dec 2004 19:57:32 -0800 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: freebsd-arch@freebsd.org Subject: Re: Adding standalone RSA code Message-ID: <41BA702C.3010909@wadham.ox.ac.uk> In-Reply-To: <20041211035012.GB93068@dragon.nuxi.com> References: <41B92CF3.2090302@wadham.ox.ac.uk> <20041211020518.GA74718@dragon.nuxi.com> <41BA6BDE.5070909@wadham.ox.ac.uk> <20041211035012.GB93068@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote:
> In other words, rather than create an RSA library that your code links
> against, just build .o's and list the .c's in your FreeBSD Update's
> Makefile. That way you can use this RSA code that you want to, but it
> isn't exposed as a consumable library in FreeBSD's {,/usr}/lib.
Ah, now I understand. FreeBSD Update is a shell script, so I'd still need
to add an rsa-verify program into /usr/sbin, but I'm quite happy to have
it statically link my RSA code rather than installing a separate library,
if that's what people would prefer. Honestly, I thought that people would
complain if I did it that way.
Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41BA702C.3010909>