Re: Seven jCIFS bug fixes from Google./Future Development
"Christopher R. Hertel" <[email protected]> Wed, 22 Jun 2016 21:52:37 -0500
| Newsgroups | gmane.network.samba.java |
|---|---|
| Message-ID | <CAPa6grJ9N2qc_UySjbdZjcJ6g7dfsdj+9ObA3FKYN0F=gksWug@mail.gmail.com> |
--001a114d764aa1c4280535e925ef Content-Type: text/plain; charset=UTF-8 Agreed. On Wed, Jun 22, 2016 at 9:14 PM, Michael B Allen <[email protected]> wrote: > On Wed, Jun 22, 2016 at 11:26 AM, Moritz Bechler <[email protected]> wrote: > > Hi, > >> If there is someone out there who would like to spearhead a new > >> development branch of jCIFS, I'd be happy to provide insight into the > >> workings of SMB. I'm particularly interested in seeing SMB2/3 support > >> added to jCIFS. > > > > RIght now we have dozens of unrelated and potentially incompatible forks > > and patchsets of jCIFS out there - that really is a waste of everybodies > > time. > > > > I think the first thing we need to do is to somehow reunite these > > efforts. If we all continue like this I guess we soon will be in a > > situation where it will just stop working with new servers (or ones > > configured for security) for all of us. > > > > I'm not sure where upstream is actually abandoned or not, any comments > > from there? > > > > A while back I started working on a fork > > (<https://github.com/AgNO3/jcifs-ng/>) featuring some major > > architectural changes, including: > > - removal of global state (one can now run multiple isolated clients) > > - more flexibility in configuration, no longer forced to use system > > properties > > - cleaner abstraction of auth mechanisms, NTLMSSP, Kerberos support > > - merged various patches > > > > This required a few API breaks. > > > > So I guess this might be a good starting point for a new development > > branch. I'd be happy to merge other improvements and fixes and am > > ultimately looking forward to adding SMB2+ support, but I don't think > > thats an effort that I can tackle completely on my own in the near > future. > > > > > > regards > > > > Moritz > > Hi Moritz, > > That all sounds great but I would like to caution anyone forking JCIFS: > > I can see there are literally 5 pages of projects on github called > "jcifs". Not "jcifs-foo" or whatever but just "jcifs". If you or > anyone else creates a fork of jcifs, please do NOT call it "jcifs". If > someone builds it and makes a jcifs-x.x.x.jar they will not be able to > identify the fork from the original! > > Mike > > -- > Michael B Allen > Java Active Directory Integration > http://www.ioplex.com/ > > -- "Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq. ubiqx Team -- http://www.ubiqx.org/ -)----- [email protected] OnLineBook -- http://ubiqx.org/cifs/ -)----- [email protected] --001a114d764aa1c4280535e925ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Agreed.<br></div><div class=3D"gmail_extra"><br><div class= =3D"gmail_quote">On Wed, Jun 22, 2016 at 9:14 PM, Michael B Allen <span dir= =3D"ltr"><<a href=3D"mailto:[email protected]" target=3D"_blank">ioplex@g= mail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style= =3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div cla= ss=3D"HOEnZb"><div class=3D"h5">On Wed, Jun 22, 2016 at 11:26 AM, Moritz Be= chler <<a href=3D"mailto:[email protected]">[email protected]</a>> wrot= e:<br> > Hi,<br> >> If there is someone out there who would like to spearhead a new<br= > >> development branch of jCIFS, I'd be happy to provide insight i= nto the<br> >> workings of SMB.=C2=A0 I'm particularly interested in seeing S= MB2/3 support<br> >> added to jCIFS.<br> ><br> > RIght now we have dozens of unrelated and potentially incompatible for= ks<br> > and patchsets of jCIFS out there - that really is a waste of everybodi= es<br> > time.<br> ><br> > I think the first thing we need to do is to somehow reunite these<br> > efforts. If we all continue like this I guess we soon will be in a<br> > situation where it will just stop working with new servers (or ones<br= > > configured for security) for all of us.<br> ><br> > I'm not sure where upstream is actually abandoned or not, any comm= ents<br> > from there?<br> ><br> > A while back I started working on a fork<br> > (<<a href=3D"https://github.com/AgNO3/jcifs-ng/" rel=3D"noreferrer"= target=3D"_blank">https://github.com/AgNO3/jcifs-ng/</a>>) featuring so= me major<br> > architectural changes, including:<br> > - removal of global state (one can now run multiple isolated clients)<= br> > - more flexibility in configuration, no longer forced to use system<br= > > properties<br> > - cleaner abstraction of auth mechanisms, NTLMSSP, Kerberos support<br= > > - merged various patches<br> ><br> > This required a few API breaks.<br> ><br> > So I guess this might be a good starting point for a new development<b= r> > branch. I'd be happy to merge other improvements and fixes and am<= br> > ultimately looking forward to adding SMB2+ support, but I don't th= ink<br> > thats an effort that I can tackle completely on my own in the near fut= ure.<br> ><br> ><br> > regards<br> ><br> > Moritz<br> <br> </div></div>Hi Moritz,<br> <br> That all sounds great but I would like to caution anyone forking JCIFS:<br> <br> I can see there are literally 5 pages of projects on github called<br> "jcifs". Not "jcifs-foo" or whatever but just "jci= fs". If you or<br> anyone else creates a fork of jcifs, please do NOT call it "jcifs"= ;. If<br> someone builds it and makes a jcifs-x.x.x.jar they will not be able to<br> identify the fork from the original!<br> <br> Mike<br> <br> --<br> Michael B Allen<br> Java Active Directory Integration<br> <a href=3D"http://www.ioplex.com/" rel=3D"noreferrer" target=3D"_blank">htt= p://www.ioplex.com/</a><br> <br> </blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig= nature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><span style=3D"= font-family:courier new,monospace">"Implementing CIFS - the Common Int= ernet FileSystem" ISBN: 013047116X<br>Samba Team -- <a href=3D"http://= www.samba.org/" target=3D"_blank">http://www.samba.org/</a>=C2=A0=C2=A0=C2= =A0=C2=A0 -)-----=C2=A0=C2=A0 Christopher R. Hertel<br>jCIFS Team -- <a hre= f=3D"http://jcifs.samba.org/" target=3D"_blank">http://jcifs.samba.org/</a>= =C2=A0=C2=A0 -)-----=C2=A0=C2=A0 ubiqx development, uninq.<br>ubiqx Team --= <a href=3D"http://www.ubiqx.org/" target=3D"_blank">http://www.ubiqx.org/<= /a>=C2=A0=C2=A0=C2=A0=C2=A0 -)-----=C2=A0=C2=A0 <a href=3D"mailto:crh@ubiqx= .mn.org" target=3D"_blank">[email protected]</a><br>OnLineBook -- <a href=3D= "http://ubiqx.org/cifs/" target=3D"_blank">http://ubiqx.org/cifs/</a>=C2=A0= =C2=A0=C2=A0 -)-----=C2=A0=C2=A0 <a href=3D"mailto:[email protected]" target=3D= "_blank">[email protected]</a><br><br></span></div></div> </div> --001a114d764aa1c4280535e925ef--