Date: Wed, 30 Dec 2020 21:34:16 +0100 From: Daniel Ebdrup Jensen <debdrup@FreeBSD.org> To: freebsd-hackers@freebsd.org Subject: Re: Project information - SMBv2+ Message-ID: <20201230203416.xr42tsdo2m7txex7@nerd-thinkpad.local> In-Reply-To: <075f31cb-dd13-778d-ed50-3ec7d6f30731@gmx.net> References: <16e5725b-ec2f-3222-d20d-fd15e597c12c@gmx.net> <dea01842-79e7-33ed-4302-28f2df51d710@quip.cz> <075f31cb-dd13-778d-ed50-3ec7d6f30731@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--i6zsmpbkywmh6xoh Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 30, 2020 at 08:24:31PM +0100, CerebrosuS wrote: > > >Am 30.12.20 um 20:05 schrieb Miroslav Lachman: >>On 30/12/2020 18:57, CerebrosuS wrote: >>>Hello at all, >>> >>>the community and developer at FreeBSD seem to know, that SMBv1 for >>>clients is nearly over and that the included mount_smbfs doesn't support >>>newer versions. So good, so far... >>> >>>So I can find multiple information about the situation, but no clear >>>path on how FreeBSD community and developer will go on to solve this >>>missing function. (Just got the information on: >>>https://wiki.freebsd.org/MateuszPiotrowski/AccessingSmbSharesWithSambaCl= ient) >>> >>> >>>This is what I am asking: >>>- Is there a project existing for solving this problem (with whatever >>>target)? >>>- What is the way to go in future? Extend mount_smbfs or support the >>>fuse-smbnetfs part to be stable and fast like mount_smbfs (buggy and >>>laggy here)? >>>- Who is mainly working on it, if a project already exist? >>> >>>I'am just interested, cause of not finding such information clearly. Is >>>there maybe a general project management list / team to see what >>>projects are going on in whatever state? >>> >>>I am a hobby developer mainly coming from chemical engineering side, >>>having some time to help. I've already written some cross platform >>>software but never related to network or on os-level. So I am motivated >>>to invest some time in getting stuff into FreeBSD, but for me, there is >>>a lack on information (see above). >>> >>>Thank you in advance for information and help. >> >>I was involved in the thread linked by Gleb. AFAIK nothing changed from >>that time. I tried something from ports but it has more problems (shares >>cannot be mounted on boot like mount_smbfs does). >>If somebody has time and skills to try to bring SMBv2 or v3 to FreeBSD >>then Apple or Solaris sources is good start. The both were using the >>same mount_smbfs (v1) as FreeBSD so one can check their sources and see >>how they evolve to v2 / v3. > >They are both using exactly the same source code as a starting point and >extend it (or rewrite it) to SMBv2? > >>But it is out of my skill. I am not >>developer. I am just an extensive user of SMB mounted shares from >>Windows servers. >That might also be my problem, cause I've never written an application >for network nor anything related to FreeBSD on os-level. But if no one >starts, nothing might change at all. > >> >>Kind regards >>Miroslav Lachman >> >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" Hi folks, Justin T Gibbs, during one of the Office Hours meetings that have been happ= ening=20 throughout the year, spoke at some length on the subject of SMBv3 as it rel= ates=20 to integraetion in the base system [1] - and suffice it to say, it's not ne= arly=20 as simple as some people seem to asume that it is. I hope that's somewhat helpful, and it's at least a little newer than what'= s=20 referenced elsewhere. [1]: https://www.youtube.com/watch?v=3DJi4ux4FWpRU&t=3D970 --i6zsmpbkywmh6xoh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEDonNJPbg/JLIMoS6Ps5hSHzN87oFAl/s5EhfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDBF ODlDRDI0RjZFMEZDOTJDODMyODRCQTNFQ0U2MTQ4N0NDREYzQkEACgkQPs5hSHzN 87rrZgf9FgJMC9miiYg/SGWx9ByL+lvGMuDHyPuY2BUFpmSAaLGUbMnt/muYyCWU 5haVomFB/49SuVmKlOG0HLmHXhCK0nCPpzkVPH5cRJZZOXK8Nub4XnnKH+He+ttH OCd2sj50Xg8xECjpmdgsr1ZdwiTGwnYwmzLPFf0k76YJfoE7/tJPsk8w6oey1rfA CeLHCyLJnV4uZWtQunnd1P18bxVusabIH83ZWOgPLTdooFbTn6Qq7hZ9eKU7iUwH xggU5EAjExS1U/+5Sqi5cNAjTisRE1aS5Rc/JpfT6cZRqCdYOdJvbF1VX4pHNd3U PdSBDUmJpPb8lIYpGdCGChwqdi15vg== =eOgT -----END PGP SIGNATURE----- --i6zsmpbkywmh6xoh--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201230203416.xr42tsdo2m7txex7>