Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Resale value of SONOS just dropped to zero. (Score 2) 134

I'm heavily invested in SONOS kit. I even offered to help them add SMB2+ support to their existing products (they didn't take me up on the offer of help).

Announcing this without having a plan to separate "legacy" models to keep them working whilst adding new features to new kit strikes me as a corporate suicide note.

The social media fury will be strong on this one... :-).

Submission + - SAMBA versus SMB: Adversarial interoperability is judo for network effects (eff.org)

Jeremy Allison - Sam writes: Before there was Big Tech, there was "adversarial interoperability": when someone decides to compete with a dominant company by creating a product or service that "interoperates" (works with) its offerings. ..
Adversarial interoperability is judo for network effects, using incumbents' dominance against them. To see how that works, let's look at a historical example of adversarial interoperability role in helping to unseat a monopolist's dominance. ..
Windows machines used the SMB protocol for file-sharing and printers, and Microsoft's support for MacOS was patchy at best, nonexistent at worst, and costly besides. Businesses sorted themselves into Mac-only and PC-only silos, and if a Mac shop needed a PC (for the accounting software, say), it was often cheaper and easier just to get the accountant their own printer and backup tape-drive, rather than try to get that PC to talk to the network. Likewise, all PC-shops with a single graphic designer on a Mac—that person would often live offline, disconnected from the office network, tethered to their own printer, with their own stack of Mac-formatted ZIP cartridges or CD-ROMs.

All that started to change in 1993: that was the year that an Australian PhD candidate named Andrew Tridgell licensed his SAMBA package as free/open source software and exposed it to the wide community of developers looking to connect their non-Microsoft computers—Unix and GNU/Linux servers, MacOS workstations—to the dominant Microsoft LANs.

Comment Re:Time for a fork (Score 2) 40

You don't need to fork the code - at least not yet. The SMB1 server is still built in, it's just no longer available by default.

In time I really want to start removing that code however, as it really complicates the underlying NTFS emulation layer inside the smbd server code.

We can be a lot cleaner and nicer as a server if we can ditch the horrid old SMB1 emulation layer.

Comment Re: better error messages? (Score 1) 40

Actually we're pretty friendly to new contributors, although the bar is higher now then it used to be years ago to get code accepted. If you want to help please.submit patches to our gitlab repo. If they pass the CI tests.ill be happy to evaluate and give feedback on them.

Cheers,

Jeremy Allison,
Samba Team.

Submission + - Samba 4.11 removes SMB1 file-sharing protocol version by default (theregister.co.uk)

Jeremy Allison - Sam writes: For Samba version 4.11.0 we'll be disabling SMB1 on the server by default. Code is still there and can be turned by on in the config file though.

From the WHATSNEW.txt change git commit:

+SMB1 is disabled by default
+---------------------------
+
+The defaults of 'client min protocol' and 'server min protocol'
+have been changed to SMB2_02.
+
+This means clients without support for SMB2 or SMB3 are no longer
+able to connect to smbd (by default).
+
+It also means client tools like smbclient and other,
+as well as applications making use of libsmbclient are no longer
+able to connect to servers without SMB2 or SMB3 support (by default).
+
+It's still possible to allow SMB1 dialects, e.g. NT1, LANMAN2
+and LANMAN1 for client and server, as well as CORE and COREPLUS on
+the client.
+
+Note that most commandline tools e.g. smbclient, smbcacls and others
+also support the --option argument to overwrite smb.conf options,
+e.g. --option='client min protocol=NT1' might be useful.
+
+As Microsoft no longer installs SMB1 support in recent releases
+or uninstalls it after 30 days without usage, the Samba Team
+tries to get remove the SMB1 usage as much as possible.
+
+SMB1 is officially deprecated and might be removed step by step
+in the following years. If you have a strong requirement for SMB1
+(except for supporting old Linux Kernels), please file a bug
+at https://bugzilla.samba.org/ and let us know about the details.

Comment Re:Android next, please (Score 1) 51

Yeah, I afree about the anti-features. It has one really good feature though, in that it uses libsmbclient to access a local fileshare, then re-exports it as a web interface to allow media players to use it. That's a killer feature for me.

I think vlc on Android can also do this, but they ship their own SMB client code I think.

Comment Re:I don't know why... (Score 1) 51

I actually don't use a Chromebook myself, I have a Linux laptop instead so can't give you screenshots.

For single sign-on you'll need to have your Chromebook joined to the AD Domain (also using Samba underneath).

Reconnection on restart isn't there yet, but is an obvious enhancement to consider (don't want to comment on future product plans).

Comment Re:I don't know why... (Score 1) 51

No problem. Samba is still a really fun and interesting program to work on ! I'm going to be up in Redmond next week working with Microsoft engineers on adding POSIX compatibility to SMB3+ and then at the SNIA Conference in Santa Clara, CA the week after giving a couple of talks, and attending the SMB3 plugfest (where we get to work out all the interoperability bugs with other engineers working on SMB).

https://www.snia.org/events/st...

See you there ! :-).

Slashdot Top Deals

NOWPRINT. NOWPRINT. Clemclone, back to the shadows again. - The Firesign Theater

Working...