I completely agree. I have occasionally had this problem with Ubuntu
samba and gave up on it, not knowing what combination finally got it
working when it did. I almost gave up on it after the last new install.
I never considered installing Nautilus in a certain order. I just did
the default
I completely agree. I have occasionally had this problem with Ubuntu
samba and gave up on it, not knowing what combination finally got it
working when it did. I almost gave up on it after the last new install.
I never considered installing Nautilus in a certain order. I just did
the default
I just tested this in Karmic and this is broken again.
I could not access a share I created through nautilus until I ran sudo
smpasswd and added my user to the smb user db.
--
Samba and system passwords should be synchronized.
https://bugs.launchpad.net/bugs/24184
You received this bug
This only occurs if you have samba installed prior to nautilus
installing it for you. See
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/460256
--
Samba and system passwords should be synchronized.
https://bugs.launchpad.net/bugs/24184
You received this bug notification because you are a
I just tested this in Karmic and this is broken again.
I could not access a share I created through nautilus until I ran sudo
smpasswd and added my user to the smb user db.
--
Samba and system passwords should be synchronized.
https://bugs.launchpad.net/bugs/24184
You received this bug
This only occurs if you have samba installed prior to nautilus
installing it for you. See
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/460256
--
Samba and system passwords should be synchronized.
https://bugs.launchpad.net/bugs/24184
You received this bug notification because you are a
I believe you will find that this bug is now resolved in hardy. :) If
you install the samba server task, or if you use nautilus-share to
manage shares, the libpam-smbpass package will automatically be pulled
in, causing passwords to be synchronized between the system and Samba
password stores
The cleanest way to do this is to not use /etc/passwd or the smb
database and switch the entire user/password infrastructure to LDAP.
This would of course be quite a large undertaking as it would affect
much more than just SAMBA, but it might be well worth it for future
growth, especially when it
Thank you Eric for your work :-) that is a nice initiative.
However, there is a caveat with your approach and the one taken in Bug 103708.
The problem is that it tends to associate a share with a credential.
Nevertheless, credentials in Samba are samba-wide, meaning there can only be
one
Huygens wrote:
Thank you Eric for your work :-) that is a nice initiative.
Glad to be of help. I'm also making trouble in the anti-spam (reputation-based)
arena and small-scale Web frameworks (learn hours, not days or weeks), and
speech recognition-based accessibility.
However, there is a
in bug 103708 Jonathan Watmough posted a small image showing where one
could put a user's button to activate what users are associated with
what shares. what Jonathan is concerned with is an important problem,
it's just not this problem. I propose adding two more fields to the
basic dialog box
A suggestion could also be that when a user set up a new share, it is asked to
specify which account can access it, and if one or some of this accounts do not
have a Samba encrypted password, a a graphical front-end to smbpasswd should
come up and ask the user to specify for those account a
https://wiki.ubuntu.com/SimpleSambaIntegrationSpec should provide a
solution to this problem, can someone please review it?
--
Samba and system passwords should be synchronized.
https://bugs.launchpad.net/bugs/24184
You received this bug notification because you are a member of Ubuntu
Bugs,
Definitely a mandatory addition to a near future release of ubuntu!!!
--
Samba and system passwords should be synchronized.
https://bugs.launchpad.net/bugs/24184
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
About the SimpleSamba spec. The major technical problem would be that it is not
possible (to the extend of my knowledge) to synchronise already set user
passwords with Samba once it is installed. The reason is that the passwords are
kept in a hash form, thus they cannot be decrypted to be sync
Samba cannot use the same back-end.
But this isn't that big of a deal, the user would just need to change
his password once before he would be allowed to use those services. UI
would have to be made to instruct the user to do so, perhaps before
enabling any file shares.
On Tue, 2007-04-10 at
And more importantly, this spec would hash the passwords by pam as users
were created initially so that every _new_ install would have working
samba users, as well as upgraded users who had changed their passwords.
I'll clarify this on the spec.
So, if you buy a new machine, do a fresh install of
I've been thinking about this problem a bit more since I filed the
initial bugs and I think password synchronization is only part of the
problem.
The initial thought was for a naïve user. A naïve user wants to export
a share so he/she can use it from another machine. They might even give
their
This is still an issue in Feisty. After setting up a new SMB share and
setting the permissions of the shared directory to global read/write,
other Ubuntu computers (those with the same username/password on them)
are able to connect to the share without problems.
However, Windows XP clients on the
** Also affects: samba (Baltix)
Importance: Undecided
Status: Unconfirmed
--
Samba and system passwords should be synchronized.
https://launchpad.net/bugs/24184
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
20 matches
Mail list logo
