[kwlug-disc] (Easy) Linux File Sharing?

unsolicited unsolicited at swiz.ca
Mon Aug 5 17:31:36 EDT 2013

On 13-08-05 12:04 PM, Tony Abou-Assaleh wrote:
> The same goes for NFS - you can restrict access to your network IP range
> but otherwise keep it open.

But also, AFAIK, another body of userid / passwords to maintain.

> Or did you want the permissions/access to auto sync across the machines
> based on the auto-communicated username/pass?

Presumably the permissions on destination would be per the userid used 
of that destination to access that destination.

Mind you, your comment reminds me not only would Samba not copy 
permissions, probably NFS too, but the only way to get them to copy / 
duplicate / ACLs would probably be PAM. (?)

> With SSH, if you set up passwordless access, you can use scp easily. The
> encryption overhead is very minimal on modern machines.

Yes, but as said, pointlessly encrypting things, aside from the 
password. Why bother with the overhead, locally, on my own network that 
I entirely control.

> On Mon, Aug 5, 2013 at 11:59 AM, Darcy Casselman <dscassel at gmail.com> wrote:
>> You don't need permissions/credentials/whatever for Samba.  You can open
>> that sucker up as wide as you want so anyone can come in.  I generally use
>> Samba (although I do put at least password credentials on it...)
>> There's also sshfs.
>> Darcy.
>> On Mon, Aug 5, 2013 at 9:10 AM, unsolicited <unsolicited at swiz.ca> wrote:
>>> I want to be able to do in Linux what I can do in windows, easily copy
>>> files machine to machine.
>>> e.g. cp {from-blah} {to-blah}
>>> Including copy file.txt \\{machine}\c$
>>> i.e. It checks my account credentials there, gives me / (root) access,
>>> and just lets me get on with my day. (Access as in can type
>>> '//{machine}/{dir}' - let permissions there determine whether I can write
>>> anything or not.)
>>> I get that Samba and NFS are out there, but IIRC each requires a separate
>>> list of accounts / passwords / permissions. It is ludicrous to scp things
>>> everywhere - no point encrypting over my local network, which I entirely
>>> control. [rcp is frowned upon due to open-text passwords, and I can accept
>>> that, but it seems it is encrypt everything (scp) or nothing (rcp) - just
>>> encrypt the password only and get on with it.]
>>> None of this mount this or that, just let me get on with it. How?
>>> {not -everything- understands / accepts smb://...}
>>> - granted, I'm taking advantage of a 'feature' of windows, if you have
>>> the same userid / password on two non-domain machines, there is no prompt
>>> for authentication. I'm OK if on Linux I have to do the same, and make sure
>>> the uid's are the same.
>>> - don't really want to go through the rigamarole of PAM, just use the
>>> local passwd files, already - even if I do figure out how to mutually
>>> replicate PAM between two machines. (Tips welcome.) Even if I had PAM, it's
>>> not clear to me what syntax to use (everywhere) for //machine/dir-hierarchy/
>>> **filename
>>> I get Windows natively understands smb and Linux doesn't (only some
>>> things understand smb://) - what does Linux natively understand that uses
>>> the local passwd file? (From past threads, some just gave up on trying to
>>> use NFS and just use Samba.)
>>> Suggestions, links?
>>> ______________________________**_________________
>>> kwlug-disc mailing list
>>> kwlug-disc at kwlug.org
>>> http://kwlug.org/mailman/**listinfo/kwlug-disc_kwlug.org<http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org>
>> _______________________________________________
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
> _______________________________________________
> kwlug-disc mailing list
> kwlug-disc at kwlug.org
> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org

More information about the kwlug-disc mailing list