similar to: samba4: samba-tool and (unix) uids

Hi all, As per Jelmer's request - in response to bug #7455 attached diff file. Please let me know what you think and if any modificationes need to be performed Regards Luk -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: newusergroupadv.diff URL:

Good Day All I need the full list of option supported by the command samba-tool create user. the online help does not provide them all, in fact I see: 8< ------------------------------------------------------------------------------------------------------------ Options: -h, --help show this help message and exit -H URL, --URL=URL LDB URL for database or target server

Hi we're busy discovering samba4 at the moment. we've installed fedora-ds as ldap backend. all install's configs and provisioning went well.. (no strange errors orso) after fireing it all up we tried to add a user and this is what we got back: ----------------------------------------- Traceback (most recent call last): File "./newuser", line 69, in <module>

Dear list, I ''m using a text input field with autocompletion . The suggestions come from a ferret index which is created by getting all the terms belonging to other indices. Here is the code: class Suggestion attr_accessor :term def self.index(create) [Person, Project, Orgunit].each{|kl| terms = self.all_terms(kl) terms.each{|term| suggestion =

On Thu, 3 May 2018 15:07:30 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Thu, 3 May 2018 10:17:48 -0300 > "Ethy H. Brito via samba" <samba at lists.samba.org> wrote: > > > > > You will never get the same IDs on the PDC and Unix domain member > > > (this isn't really a problem) > > > > I know that. But

Hello, on Mon, 07 Dec 2009 01:13:19 -0800 Eric Woltermann posted: > for some weeks now I am trying to set up Samba4 (alpha9) with an OpenLDAP 2.4.17 backend as an AD PDC for my XP/7 clients. It was working for some time with Samba's integrated LDAP facility, however I could not figure out how to use this database e.g. to authenticate my IMAP users against (bind-dn, port etc.). OpenLDAP

Hello, I am working on migrating from OpenLDAP using the inetOrgPerson schema to Samba4. I would like to continue to provide backwards compatibility with our existing authentication service. In OpenLDAP, users are all contained inside the People organizational unit and referenced by uid, for example: dn: uid=myuser,ou=People,dc=example,dc=com When using samba-tool to add a user, it places the

I've got a somewhat special domain (servers only, no clients, for unified passwords stored in ldap and unix passwords are in there too), and I'm looking at my directory and there are a few things I don't quite understand, or that I need some clarification on.. 1) these "Domain Admins" and "Domain Guests" and "Domain Computers" groups.. do they NEED

Hi, In my LAN Iam trying to make following setup: - All the traffic generated by 10.0.2.1 should go to 10.0.2.11, If the destination of this traffic is internet than it should be placed on its interface eth1. Outgoing traffic on eth1 should be shaped.For this I am using fw filters and cbq. _______ 10.0.2.1 -------> 10.0.2.11(eth0 )----| A

On Thu, 3 May 2018 08:40:37 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 2 May 2018 19:21:46 -0300 > "Ethy H. Brito" <ethy.brito at inexo.com.br> wrote: > > This is where it is all going wrong, Your PDC isn't using LDAP, so > you will have to rely on the winbind 'rid' backend. The lines below are > wrong in several

Hello, When trying out (g)pxelinux using TFTP URLs and the '<host>::<path>' syntax, pxelinux seemed to "hang". Some printf debugging and tcpdump revealed that it looped in the timeout after sending the TFTP RRQ. Further investigation revealed, that if a plain IP address (e.g. "tftp://12.34.56.78/something") is used, the byte order is not converted from host

We recently upgraded our PDC from Debian 4 to Debian 5. That entailed an upgrade of Samba from 3.0.24 to 3.2.5. Since the upgrade we've had a very specific problem connecting to shares on a commercial NAS running Samba 3.0.34. The problem happens when users try to connect to shares from standalone servers--e.g., Windows XP Pro boxes that we use for testing. From those boxes users should be

On 2018-08-21T06:21, Stef Bon <stefbon at gmail.com> wrote: > Op di 21 aug. 2018 om 06:04 schreef Stef Bon <stefbon at gmail.com>: > > > > Hi, > > > > I'm looking for a procedure (on paper first) to provide users on hosts > > session keys to login to servers providing services like file, print > > or even access to internet or a sql db. >

How about using the existing OpenSSH client's PKCS#11 support to isolate keying material in a dedicated process? A similar approach, "Practical key privilege separation using Caml Crush", was discussed at FOSDEM'15 with a focus on Heatbleed [1][2] but the ideas and principles are the same. Now this is easily done using the following available components: - SoftHSM to store

While investigating an unrelated issue I discovered that winbind is completely confused or corrupt on one machine, a domain member server running Samba 3.0.34: # wbinfo -u NAS\backup-private NAS\backup-public ... administrator guest michaell ... administrator administrator michaell ... administrator administrator guest Segmentation fault NAS is the name of the domain member server; the name of

Hello, Is there a way to define an environment for the prospective nodes in nodes.pp (maybe a default node?) I''d like to be able to define it there and then have my puppet module configure the node puppet.conf (erb template) based on the parameters that’s passed on from the master. Possible? Thanks, Will -- You received this message because you are subscribed to the Google Groups

Hi, Someone told me that DSA keys were being deprecated with OpenSSH 7.0. The only reference I could find about this topic on openSSH site is on the legacy page: ?OpenSSH 7.0 and greater similarly disable the ssh-dss (DSA) public key algorithm. It too is weak and we recommend against its use.? There is no explanation about the weakness. But more than that, I could not find any mention

Hello, in light of the recent CVE-2016-0777, I came up with the following idea, that would have lessened its impact. Feel free to ignore or flame me, maybe its stupid or I missed something :) - private key material should only ever be handled in a separate process from the SSH client. ssh-agent (maybe slightly extended) seems the logical choice. - in places where the client currently reads

On Sat, Nov 26, 2016 at 1:16 AM, Alexander Wuerstlein <arw at cs.fau.de> wrote: [...] > Afaik its because DSA key size has (for very weird reasons admittedly: > FIPS 186-4) been limited to 1024 bits which is considered weak nowadays. Use of DSA within the SSH protocol requires the use of SHA1, which is 160 bits (80 bits against a birthday attack) and is reaching its use-by date. This

On Thu, 3 May 2018 12:54:52 -0300 "Ethy H. Brito" <ethy.brito at inexo.com.br> wrote: > On Thu, 3 May 2018 15:07:30 +0100 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On Thu, 3 May 2018 10:17:48 -0300 > > "Ethy H. Brito via samba" <samba at lists.samba.org> wrote: > > > > > > > > You will