Date: Tue, 22 Jan 2002 18:34:07 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: Dag-Erling Smorgrav <des@FreeBSD.org>, Mark Murray <markm@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/share/mk bsd.libnames.mk Message-ID: <20020122183407.A46781@sunbay.com> In-Reply-To: <200201212043.g0LKh2J19576@freefall.freebsd.org> <200201212042.g0LKgPt19466@freefall.freebsd.org> References: <200201212043.g0LKh2J19576@freefall.freebsd.org> <200201212042.g0LKgPt19466@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline :-( It's a real pita to see this change go in after I've spent so much time hacking on this and was told to hold off for a while by Mark Murray. The relevant mailing threads (most of them you were CC:ed to) were called "PAM, libssh, and all that" and "libssh[_pic].a question", which produced two (different approach) patches. Also attached is my last public posting on the topic, which got unanswered. Please back your changed out, look at my proposed patches, and comment on them. My patches fix much more problems that the below changes, in a better way, and make things actually "run", not only "compile". Please re-read my message <20011210210742.B52807@sunbay.com> in the "libssh[_pic].a question" thread and the libssh.patch.log file from my freefall patch page (see mail attached) before replying. I'd be more than happy to commit my patch myself after a discussion that was requested by Mark Murray in his last (private) message to me: On Mon, Dec 24, 2001 at 02:56:26PM +0200, Mark Murray wrote: > > > Ahh yes. I remember that. It is a sticky problem. Your points are > > > well made, but I don't think we should do anything rash just yet. > > > > > > So my position on this modifies to - "Please leave the libssh > > > internal thing for a while (at least until we can bikeshed it > > > properly). Documenting it as a proper API may be the way to go in > > > fact". > > > > > Sorry, but I don't get it. libssh is not "internal" currently, > > and my patch (that I want to commit) makes it an internal one. > > Does this mean you are happy with me committing the whole patch? > > No. I am not happy with this part (yet). It needs some discussion IMO. On Mon, Jan 21, 2002 at 12:42:25PM -0800, Dag-Erling Smorgrav wrote: > des 2002/01/21 12:42:25 PST > > Modified files: > share/mk bsd.libnames.mk > Log: > Add the necessary dependencies and linker flags for linking with a > static PAM library that includes pam_ssh. > > Sponsored by: DARPA, NAI Labs > > Revision Changes Path > 1.49 +6 -3 src/share/mk/bsd.libnames.mk On Mon, Jan 21, 2002 at 12:43:02PM -0800, Dag-Erling Smorgrav wrote: > des 2002/01/21 12:43:02 PST > > Modified files: > lib/libpam/libpam Makefile > Log: > Link pam_opieaccess, pam_self and pam_ssh into the static library. > > Sponsored by: DARPA, NAI Labs > > Revision Changes Path > 1.24 +3 -0 src/lib/libpam/libpam/Makefile -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --HlL+5n6rz5pIUxbD Content-Type: message/rfc822 Content-Disposition: inline Date: Wed, 12 Dec 2001 13:26:49 +0200 From: Ruslan Ermilov <ru@FreeBSD.org> To: current@FreeBSD.org Subject: pam_ssh support for static PAM library Message-ID: <20011212132649.D32012@sunbay.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.23i Hi! There's a number of build problems exists with libssh, pam_ssh, and libpam triple. The major issue being that the static PAM library, libpam.a, doesn't currently support pam_ssh. There have been a semi-private discussion taking place between me and Mark Murray on the subject, and I've prepared a set of patches to address these issues. First approach proposed was to make libssh a "standard" FreeBSD library, in that sense that it has its name in bsd.libnames.mk namespace, and is installable under /usr/lib, and is available for dynamic linking. This approach was rejected, because libssh is believed to be of no common interest to be available under /usr/lib, in that sense when we call such a library "internal". The latest patch on the subject is believed to fix all these issues, while still preserving libssh from being visible under /usr/lib. I've already sent a notification to Mark, and he promised to look into my patch during the next week or so. For those also interested, I've put my patch and the detailed log here: http://people.FreeBSD.org/~ru/patches/libssh.patch http://people.FreeBSD.org/~ru/patches/libssh.patch.log In order to test it without a full "buildworld", you'll have to proceed in this order: 1. Install updated bsd.lib.mk and bsd.libnames.mk. 2. Build secure/lib/libssh. 3. Build and install lib/libpam. Now you're ready to build/install any PAMified stuff statically, and pam_ssh should be available. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --HlL+5n6rz5pIUxbD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020122183407.A46781>