search for: juser

Greetings running dovecot for my first time on an OSX 10.6 server. after a reboot, several users are not able to Authenticate. here is a sample Oct 5 20:22:32 hsmail dovecot[2142]: auth(default): od(juser,127.0.0.1): auth mech=CRAM-MD5 Oct 5 20:22:32 hsmail dovecot[2142]: auth(default): od(juser,127.0.0.1): username=juser, challenge=<6757250558559635.1286324552 at hsmail.beth.k12.pa.us>, response=26b23b30128bba4f9ba3aca261ec764e Oct 5 20:22:32 hsmail dovecot[2142]: auth(default): od(juser,12...

...ng like this: Boot a Live CD. (eventually one I customize with a nifty script to do all of this) Now I have support for my pcmica nic. Now do the part that PXE would do: dhcpclint, get an IP, netmask etc. and a file name (pxelinux.0) and maybe a server name. use tftp client to get that file: juser at v550b:~$ tftp shaz tftp> get pxelinux.0 run it. That should turn around and ftp> get pxelinux.cfg/default and give ma a boot: which will let me select: label ubuntu-edgy-alternate-hands-off kernel ubuntu/edgy/alternate/install/netboot/ubuntu-installer/i386/linux appen...

I am trying to handle in my user class assigning user to groups, and handling that some groups might not be defined for that node. Example here is handling a non-datase node, "juser" fails with "Error: Failed to apply catalog: Parameter groups failed on User[juser]: Group names must not be empty. If you want to specify "no groups" pass an empty array" even in the notice and logs the correct value ("wheel") is logged? I was inital just...

...populate ldap, and; 2) to create users and machines. This seems to work fine. I've also installed PhpLdapAdmin, as my users are not command line savvy. I want them to use that tool to create new users and machines. Here's the issue: If I enter the command "smbldap-useradd -a -m -M juser -g "Domain Users" -G "Domain Admins" -G "Administrators" -c "Joe User" juser" (beginning and ending parens for clarity), I do indeed create the type of user I'm trying to create. And, that user appears in the list of users in PhpLdapAdmin. However,...

...Currently this is the behaviour: $ ssh -i "pass.pem" myserver123.amazonaws.com Permission denied (publickey). It of cause works if I do: ssh -i "pass.pem" ubuntu at myserver123.amazonaws.com What I would like to see is: $ ssh -i "pass.pem" myserver123.amazonaws.com juser at myserver123.amazonaws.com Permission denied (publickey). This means, we would realise that "juser" didn't have an account on that VM at Amazon. Sound reasonable? -- You are receiving this mail because: You are watching the assignee of the bug.

...is, we have some instances where users' AD accounts are not the same as their unix id's (matching them up at this point is not an option). Is there a way to tell winbind to look at the uid attribute in AD rather than the sAMAccountName for a Unix user name? For example, if my AD login is JUser but my uid in AD is defined as juser1, is it possible to tell the unix systems running winbind to log me in with juser1 instead of juser? If not, I can simply use the LDAP interface into AD for those systems, but I'd like to try and keep everything consistent, if possible. Thanks! Greg

I am working in an environment with an HP-UX NIS that my Red Hat ES 4.x system is using for Unix access controls. My Red Hat system is serving as an NFS server for the HP-UX users who also could be Windows users coming from a Windows Server 2003 active directory. I have tested some configurations of SAMBA using winbind, but I don't get the results I want. What happens when using winbind

...ix = ou=Groups ldap admin dn = cn=directory manager ldap ssl = on # not sure what these do, to be honest idmap uid = 10000-20000 idmap gid = 10000-20000 # include extra user configuration. For instance, if you wanted to # turn up the log level for John User, you could create a file called # 'juser.inc' (or whatever John's username is) and add a 'log level' # line to it. This include statement has to be here, at the end of # the [global] section and before any of the shares, so that it can # override any global configuration directives, but won't be # considered part of a...

...it is very > important that you triple check that the binary files you are using now > (in your "target" device/image) are exactly those I just posted. These > packages are from current Debian "Testing" repo. > I'm pretty sure everything is coming from testing: juser at dc10b:~/temp$ apt-cache policy syslinux syslinux-efi syslinux-common |grep 500 *** 3:6.04~git20171011.af7e95c3+dfsg1-5 500 500 http://deb.debian.org/debian buster/main amd64 Packages *** 3:6.04~git20171011.af7e95c3+dfsg1-5 500 500 http://deb.debian.org/debian buster/main amd64...

On Sat, Dec 1, 2018 at 2:46 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > it works. (boots into the d-i installer, I don't care if the installer > > is missing stuff, booting it is all we care about here. > > > OK, so let's add complexity (but not the whole thing, not yet). > > We already have: > > target > ??? EFI > ? ???