LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  August 2004

XROOTD-L August 2004

Subject:

Re: xrootd meeting - Tuesday, 17 August, 2004

From:

Fons Rademakers <[log in to unmask]>

Date:

19 Aug 2004 11:09:49 +020019 Aug 2004 11:09:49 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (124 lines)

Hi Gerri,

  I propose the first priority to be a special target in the xrootd
Makefile for only building the security modules and making sure that
these can be compiled everywhere. The client code can still depend on
this but since it can be build everywhere this will not be an issue. In
parallel we continue with the port of the xrootd server proper.

Cheers, Fons.




On Wed, 2004-08-18 at 19:08, Gerardo Ganis wrote:
> Hi Fons,
>
> Of course, the final aim should be at a complete build of
> the client on all the platforms.
>
> A separate target to make only the XrdSec&C shared libs
> can be implemented quickly: the porting of these modules
> (and XrdOuc, used by them) to Win32 will surely take longer,
> since there are a few things to be adapted ...
>
> I think that modifying the way the client uses XrdSec, so that
> it does not require those libraries at build time, is anyhow
> a good thing, because it reduces the minimal client dependence
> on the server to the availibility of a few header files.
> It should also (potentially) allow to build the client on a larger
> number of platforms already from now.
>
> Then we could concentrate on the porting of XrdSec and XrdOuc to
> Win32.
>
> What do you think?
>
> Cheers, Gerri
>
>
> On 18 Aug 2004, Fons Rademakers wrote:
>
> > Yes, the absolute priority should be to port xrootd to all platforms
> > except for Win32 (rootd also was never ported to Win32 either). However,
> > the client definitely should work on Win32 (although some strong
> > authentication modules might be missing if the supporting libs are not
> > available on win32). So if we could include a special target in the
> > xrootd Makefile for the authentication modules that can build on any
> > platform, incl Win32, we are on the right way.
> >
> > -- Fons
> >
> >
> > On Wed, 2004-08-18 at 14:28, Peter Elmer wrote:
> > > Hi Fons,
> > >
> > > I think had planned to port the full xrootd build to all of the relevant
> > > unix platforms, but, like rootd, weren't planning on porting it to Win32.
> > > Perhaps we can at least make the security modules build on Win32, though,
> > > which would at least allow for the full functionality of the client. (One
> > > could imagine some build option for xrootd which just build the subset on
> > > Win32, which should be easier than the full port.) Andy, what do you think?
> > >
> > > Pete
> > >
> > > On Wed, Aug 18, 2004 at 02:21:54PM +0200, Fons Rademakers wrote:
> > > > On Wed, 2004-08-18 at 12:18, Gerardo Ganis wrote:
> > > > > > On Tue, Aug 17, 2004 at 12:10:16PM +0200, Fons Rademakers wrote:
> > > > > > > The main issues I've at the moment are:
> > > > > > >
> > > > > > > - build procedure of sec modules separate from xrootd.
> > > > > > > Currently we can build xrootd and therefore the sec modules only
> > > > > > > on Linux and Solaris, however we really require the netx client to be
> > > > > > > able to build on all ROOT supported platforms, incl Win32. Since for
> > > > > > > the time being the building of the client is linked to the building
> > > > > > > of the server we have the client only on Linux and Solaris.
> > > > > >
> > > > > > Gerri and I talked about this yesterday. He thought there were two
> > > > > > problems:
> > > > > >
> > > > > > o Something in the way the packages are built within ROOT which made the
> > > > > > netx client build dependent on having built xrootd. Do you have some
> > > > > > mechanism in the ROOT builds which just skips rootd/xrootd on platforms
> > > > > > where it is not supported (e.g. Win32)?
> > > > > >
> > > >
> > > > Currently they are dependent since the authentication modules are part
> > > > of the xrootd tar ball and are build by the xrootd makefile. These
> > > > authentication modules should be independent from xrootd and be ported
> > > > to all possible platforms (ideally xrootd should be ported to all
> > > > platforms so that this issue becomes moot).
> > > >
> > > >
> > > > > > o There was an explicit dependency on libXrdSec.so. It seemed like it
> > > > > > should be possible to make this load instead as a plugin.
> > > > >
> > > > > This is almost ready.
> > > > >
> > > > > >
> > > > > > Hmm, one thing occurs to me: how is the security stuff handled for Win32
> > > > > > if the xrootd server isn't built?
> > > > >
> > > > > I am modifying things in such a way that, when the server cannot be built,
> > > > > the protocol header files are extracted from the server source, so that
> > > > > they can be found when building the client.
> > > > > Of course, since lib/libXrdSec.so is not there, the client will not able
> > > > > to satisfy strong authentication requests from the server; however it should
> > > > > work if no authentication or host authentication are required.
> > > > >
> > > > I rather have a solution where the authentication modules are ported to
> > > > all platforms and delivered as a separate tar. However, porting xrootd
> > > > to all platforms should be the priority and will solve this problem even
> > > > better.
> > >
> > >
> > >
--
Org: CERN, European Laboratory for Particle Physics.
Mail: 1211 Geneve 23, Switzerland
E-Mail: [log in to unmask] Phone: +41 22 7679248
WWW: http://www.rademakers.org/fons/ Fax: +41 22 7679480



Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use