I still would really like somebody to at least give it a try!

But if I don't hear by the end of the day, I'll go ahead and merge into
trunk and the release branch.

Karl


On Wed, Apr 24, 2019 at 11:49 AM Markus Schuch <markus_sch...@web.de> wrote:

> Hi Karl.
>
> all windows shares in my reach were migrated to O365 services some months
> ago, so i am unfortunately unable to help here, sorry.
>
> IMHO we should ship because anyone using the abandoned jcifs based
> connector relies on vulnerable cifs protocols (if i am correct).
>
> Cheers
> Markus
>
>
> Am 24. April 2019 12:08:21 MESZ schrieb Karl Wright <daddy...@gmail.com>:
> >I'm still waiting for somebody to give the new Jcifs code a try before
> >spinning the release.  There apparently are plenty of people who want
> >us to
> >do work on the connector but who are unwilling to actually exercise it
> >when
> >that work is completed.
> >
> >I suppose I can integrate it and we can ship it.  Some people might be
> >surprised though. :-)
> >
> >Karl
> >
> >
> >On Mon, Apr 22, 2019 at 7:23 AM Karl Wright <daddy...@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> It came to my attention last week that there's a new version of Jcifs
> >> available, which has some API changes and is thus not backwards
> >compatible
> >> with the old version.  But it also has significant new features
> >added.
> >>
> >> I updated the code for it in
> >> https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-1498.
> > I
> >> haven't had opportunity to exercise it, so I'm hoping one of our
> >jcifs
> >> users will have a look with an eye towards including this new code in
> >the
> >> 2.13 release (for which I am about to push the button within the next
> >few
> >> days).  Any takers?
> >>
> >> Karl
> >>
> >>
>
> --
> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
> gesendet.

Reply via email to