Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] setuid on jetty9
this seems to have worked well

https://oss.sonatype.org/content/repositories/jetty-280/
https://oss.sonatype.org/content/repositories/jetty-281/

I moved the setuid stuff to our toolchain modules and pushed out the release from my mac, and then updated to the release tag and pushed up the linux so files to the second repository above...

In the loading code I added a bit that will load up the right so file based on the OS you're running on (providing that is osx or linux at this point).

version wise I made these 1.0.0 and have the distribution updated locally for it and it builds fine...I'll want these to percolate out into central before I smoke the jetty-setuid module on master and update the distribution to use this toolchain stuff.  The distribution is a lot cleaner this way, I like it...no profiles :)

just release those two repositories so they may not be there anymore...but I'll update jetty master to use this and smoke the jetty-setuid stuff in the morning.

and then update the documentation for usage and release procedure!

cheers,
jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx


On Wed, Dec 5, 2012 at 10:08 AM, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:
well, in the SetUID class there is a mess of different loading strategies so my idea was to us System to get the os type then try and load it accordingly

so running on osx would look for libsetuid-osx.so and so on and so forth for different architectures

I'll work on wiring that up today

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Wed, Dec 5, 2012 at 9:51 AM, Karl Ostendorf <karl@xxxxxxxxxxxxx> wrote:
Good point, the GPL changes things; did not know that.

In any case, my recent attempts at compiling the native library on OSX were as simple as "mvn package" so I look forward to testing the 9.x version of setuid again once it has moved to its new home.

Eventually, I'd like to find a way to embed the native libraries for both Linux and OSX in a JAR file and then extract and load the appropriate one to/from a temp file at runtime. I'll let you know how it works out.
On 5 Dec 2012, at 15:12, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:

> Unfortunately, the JNA license is GPL.
> https://github.com/twall/jna/blob/master/LICENSE
>
> Getting GPL licensed code approval from the Eclipse lawyers is extremely difficult, and can take up to 5 years to get an answer from them.
>
> This effectively makes using GPL libraries forbidden at Eclipse.
>
> --
> Joakim Erdfelt <joakim@xxxxxxxxxxx>
> webtide.com
> Developer advice, services and support
> from the Jetty & CometD experts
> eclipse.org/jetty - cometd.org
>
>
>
> On Wed, Dec 5, 2012 at 2:24 AM, Karl Ostendorf <karl@xxxxxxxxxxxxx> wrote:
> Hi,
>
> I think moving setuid to -toolchain and a separate release cycle is a good idea, however, I was wondering why not move to a JNA solution instead of sticking with JNI? JNA would alleviate us from having to compile and deploy the native binary, is an actively supported project and also nicely mavenized.
>
>
> --
> karl | karl@xxxxxxxxxxxxx | http://ostendorf.com/
>
> On 5 Dec 2012, at 00:04, Jesse McConnell <jesse.mcconnell@xxxxxxxxx> wrote:
>
> >
> > I have wired up setuid for jetty 9 distribution but I feel it kinda sucks still and have an alternative idea I want to bounce of folks for M4.
> >
> > How about I move the jetty setuid stuff to jetty-toolchain so we can release them on a separate release cycle...which means we can release both linux and osx and whatever other setup (SunOS, etc) that we have access to...and then we can depend on these direct versions and pull those into our jetty-distribution and then make the jetty-setuid-java setup a bit smarter in loading the right OS library?  The Server api is quite stable so these things don't need to release very often anyway...
> >
> > as it stands right now with what I have committed we release on linux so the the jetty-distribution setuid bits will work on _linux_ and if you want osx you need to checkout jetty from git and build the distro there, or build just that one lib and manually replace it
> >
> > thoughts?
> >
> > jesse
> >
> > --
> > jesse mcconnell
> > jesse.mcconnell@xxxxxxxxx
> > _______________________________________________
> > jetty-dev mailing list
> > jetty-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev

_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev


Back to the top