Hi all, c. april 2016….. Jeremie wrote:
> on Tuesday the samba team will release major security patches. You may > have heard of > > http://badlock.org/ <http://badlock.org/> > > samba-4.1 is EOL upstream, thus they won't release a new version. > > At $WORK we've been recognized as samba vendors, meaning that we have > access to the bug, diffs and upcoming tarballs. The diff applied to > 4.2+ is huge, I don't think it's reasonable for us to try to backport > it. Right now I'm trying to upgrade to 4.3.6... If memory serves me, there was an issue at the time linking to lib archive and as no one else was testing and didn’t use the feature, I think it was agreed to look at this at a later date. So, this was removed in the middle of a major Samba security, coupled with moving to newer major versions, in a short period of time. I think that covers it. I have no issue if the feature makes its way back into the port. Ian McWilliam > On 4 Jul 2023, at 9:42 pm, Jeremie Courreges-Anglas <[email protected]> wrote: > > On Mon, Jul 03 2023, Alexander Klimov <[email protected]> wrote: >> Hello port devs! > > Hi, > >> Any reason why net/samba is built explicitly --without-libarchive? >> That disables the manpage-documented -TcF option (tar backup creation). >> Btw. s/--without-libarchive/--with-libarchive/ made it working for me >> (x86_64). > > Looking at cvs blame and cvs log, there were many changes between 4.1.23 > and 4.3.6. I probably disabled libarchive support out of a judgement > call, knowing I had bigger fish to fry (security updates). > > If the current lack of libarchive support is a problem then we can > probably add it. Can you please confirm that tar/libarchive support in > smbclient is fully usable to backup and restore files on a share? > > PS: if a port has a maintainer then do Cc them. (+cc Ian) > -- > jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
