or the commands useradd and usermod. With the first, the
> system administrator is able to force the system to create a new user
> with an ID that already exists, which is related to another user.
>
> One effect I would expect after using useradd with this option is that
> files and direct
> /usr/local/bin/bash (or whatever). Then administrators are able to log
> in as 'toor' to get bash as the default shell.
I've seen variants of this as well, but usually you do it by running vipw
to edit the passwd file (or its BSD equivalent) directly. Who's got
time to waste learning a bunch of
On 22 February 2018 at 21:12, MarkusHiereth <translat...@hiereth.de> wrote:
> Hello,
>
> when updating the German translations of the shadow package, I
> encountered strange things in the documentation. For example an option
> --non-unique for the commands useradd and us
On Thu 22 Feb 2018 at 22:12:44 (+0100), MarkusHiereth wrote:
> Hello,
>
> when updating the German translations of the shadow package, I
> encountered strange things in the documentation. For example an option
> --non-unique for the commands useradd and usermod. With the firs
On Thu, Feb 22, 2018 at 10:12:44PM +0100, MarkusHiereth wrote:
>
> Has anybody an idea about the purpose of such an option?
>
Hi Markus,
I have seen this used on old UNIX or BSD systems to create a second root
account. For example, the standard default root account is set to use
some old sh or
Hello,
when updating the German translations of the shadow package, I
encountered strange things in the documentation. For example an option
--non-unique for the commands useradd and usermod. With the first, the
system administrator is able to force the system to create a new user
with an ID
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry about late reply, got a bit busy with other things.
On 11/07/2014 11:43 PM, Reco wrote:
Hi.
I'd try adding some memory (or swapspace) to this VM to satisfy
mremap's wish to remap to exactly 8G virtual memory.
Reco
Tried this, set the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 03:43 PM, Don Armstrong wrote:
No, just don't send the whole core dump itself (the file called
core) to the BTS (or this mailing list). It almost certainly has
your machine ldap password in it.
that makes sense, wont do that,
On Sun, 09 Nov 2014, Joris Bolsens wrote:
Where do i find the object file for libnss-ldap? I tried running nm -a
on pretty much every file I could find with libnss-ldap in the name
and it said it didn't recognize the file type.
It should be symlinked from /lib64/libnss_ldap.so.2 or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/09/2014 12:55 PM, Don Armstrong wrote:
On Sun, 09 Nov 2014, Joris Bolsens wrote:
Where do i find the object file for libnss-ldap? I tried running
nm -a on pretty much every file I could find with libnss-ldap in
the name and it said it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/07/2014 11:43 PM, Reco wrote:
So, chances are - you've found a bug.
Awesome, where/how should I report it?
and memory info on top:
KiB Mem: 2061128 total, 263680 used, 1797448 free,75180
buffers KiB Swap: 2094076
Hi.
On Sat, 08 Nov 2014 01:02:25 -0800
Joris Bolsens jo...@linux.com wrote:
So, chances are - you've found a bug.
Awesome, where/how should I report it?
Install reportbug package. Invoke 'reportbug passwd'.
The rest of the process will be explained to you by the reportbug.
Reportbug
On Fri, 07 Nov 2014, Joris Bolsens wrote:
Ran into a bit of a strange error with useradd today, whenever i run
useradd I get a Segmentation fault.
Before filing a bug, please
1) Enable coredumps
2) Get a coredump
3) Backtrace it
4) Install any missing -dbg packages which provide symbols
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, pretty new to linux still. put a few questions in-line.
On 11/08/2014 09:39 AM, Don Armstrong wrote:
Before filing a bug, please
1) Enable coredumps
Did some googling, I have to recompile the kernel for this?
the one thing i did find on
thing i did find on how to do it without was for the fedora
kernel.
Nah. All you have to do is something like the following:
ulimit -c unlimited;
useradd foo;
gdb /usr/sbin/useradd core;
bt full;
or similar.
You'll also want to install libc6-dbg gdb; and similar.
This will give you an idea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 11:16 AM, Don Armstrong wrote:
ulimit -c unlimited; useradd foo; gdb /usr/sbin/useradd core; bt
full; or similar.
You'll also want to install libc6-dbg gdb; and similar.
This will give you an idea of where the code
map: Input/output error.1`
# gdb /usr/sbin/useradd core
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY
symbols for (and unfortunately, they're not currently available).
apt-get build-dep libnss-ldap;
DEB_BUILD_OPTS=nostrip,noopt apt-get source -b libnss-ldap;
will give you those symbols.
Then you can rerun /usr/sbin/useradd foo; and re-analyze the coredump.
Please double check the bt full; output
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 12:16 PM, Don Armstrong wrote:
Please double check the bt full; output for any obvious password
strings too before posting to this mailing list. [I should have
told you to do that too, but I don't see any below, so you should
be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/08/2014 12:16 PM, Don Armstrong wrote:
apt-get build-dep libnss-ldap; DEB_BUILD_OPTS=nostrip,noopt
apt-get source -b libnss-ldap;
will give you those symbols.
Then you can rerun /usr/sbin/useradd foo; and re-analyze the
coredump
On Sat, 08 Nov 2014, Joris Bolsens wrote:
Not sure what you mean by this, don't post the full output of the
command?
No, just don't send the whole core dump itself (the file called core) to
the BTS (or this mailing list). It almost certainly has your machine
ldap password in it.
On Sat, 08 Nov
Ran into a bit of a strange error with useradd today,
whenever i run useradd I get a Segmentation fault.
I tried running fsck as i read it might be due to corrupt filesystem, but that
didn't report any problems.
I reinstalled the passwd package, also to no avail.
I ran an strace and it seems
it seems that using the adduser works fine, not sure why i didn't think to try
that before.
However I am still curious why this occurred.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On 11/07/2014 09:04 PM, Joris Bolsens wrote:
Ran into a bit of a strange error with useradd today,
whenever i run useradd I get a Segmentation fault.
I tried running fsck as i read it might be due to corrupt filesystem, but that
didn't report any problems.
I reinstalled the passwd package
and such), do you think that
could have something to do with it?
On 11/07/2014 08:26 PM, Marty wrote:
On 11/07/2014 09:04 PM, Joris Bolsens wrote:
Ran into a bit of a strange error with useradd today, whenever i
run useradd I get a Segmentation fault.
I tried running fsck as i read it might be due
On 11/07/2014 11:29 PM, Joris Bolsens wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No idea, that's just what i got when I ran the command, I left out a
bit at the top that did the ldap lookups, that all looked find and
didn't want to include that as 1) dont think it's relevant and 2)
Hi.
On Fri, 07 Nov 2014 18:04:25 -0800
Joris Bolsens jo...@linux.com wrote:
skip
mremap(0x7f239914d000, 4294971392, 8589938688, MREMAP_MAYMOVE) = -1 EFAULT
(Bad address)
It goes downhill from here. Apparently useradd does not checks a return
status of mremap, and, according to the mremap(2
.
For not so much involved like me, adduser is a friendlier interactive
frontend to useradd. At least, this is my impression and that is why I
used it for Debian Reference.
I google and find interesting old post here.
Subject: Re: adduser, useradd: are there any differences
From: Peter J. Holzer
right.
usermod makes changes to user.
useradd is not interactive, so makes an automated script for adding many
users more possible to write. including setting nonstandard home directory
or extra groups.
adduser is interactive but does not let you put a user in multiple groups,
i don't think
On 11/25/12, Wolf Halton wolf.hal...@gmail.com wrote:
right.
usermod makes changes to user.
useradd is not interactive, so makes an automated script for adding many
users more possible to write. including setting nonstandard home directory
or extra groups.
adduser is interactive but does
useradd -d /home/teste -c Teste -g grupoteste -s /bin/bash -p 'erty#12'
-m testes
Alguem sabe como posso trocar o -g grupoteste pelo numero de id do grupo
?
li e reli o man e pesquisei na internet mas nao estou achando nada a este
respeito
--
Att
Anderson Bertling
Anderson,
De acordo com o man do adduser é possível sim utilizar o gid numérico para
a criação
de um novo usuário.
Veja no link:
http://linux.die.net/man/8/useradd
o parâmetro -g, --gid GROUP
-g, --gid GROUP
The group name or number of the user's initial login group. The group name
must exist
Em Thu, 16 Aug 2012 08:07:32 -0300
Anderson Bertling andersonbertl...@gmail.com escreveu:
useradd -d /home/teste -c Teste -g grupoteste
-s /bin/bash -p 'erty#12' -m testes
Alguem sabe como posso trocar o -g grupoteste pelo
numero de id do grupo ?
li e reli o man e pesquisei na internet
The script I'm using fails at the useradd command with the following message:
(gksudo:2942): GLib-CRITICAL **: g_str_has_prefix: assertion `str != NULL'
failed
The useradd command is:
self.do_run_in_chroot(useradd -s %s -c \'%s\' -G sudo -m %s % (/bin/bash,
setup.real_name, setup.username
On Thu, 12 Apr 2012 01:11:49 -0500, Jason Hsu wrote:
The script I'm using fails at the useradd command with the following
message: (gksudo:2942): GLib-CRITICAL **: g_str_has_prefix: assertion
`str != NULL' failed
The useradd command is:
self.do_run_in_chroot(useradd -s %s -c \'%s\' -G sudo
I would like to know if it's possible when creating a new user with
the '/usr/sbin/useradd' script to set the users home directory
permissions to 700 rather than the Debian default of 755? I don't
understand why Debian does this not do I really care to debate it but
I don't like users being able
-Original Message-
From: Carlos Mennens [mailto:carlosw...@gmail.com]
Sent: Wednesday, 17 March, 2010 09:36
To: Debian
Subject: Change Useradd Behavior
I would like to know if it's possible when creating a new user with
the '/usr/sbin/useradd' script to set the users home
Carlos,
If you set the default umask in /etc/login.defs , useradd will obey this
when creating home directories. Try setting UMASK 077 in /etc/login.defs .
Alternately, you can user the higher level adduser tool, which has it's
own configuration setting for world-readable home directories
(dpkg
If I change the DIR_MODE=0700 in /etc/adduser.conf, will that also be
honored when using 'useradd'?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org
On Wed, 17 Mar 2010 13:35:39 -0400 (EDT), Carlos Mennens wrote:
I would like to know if it's possible when creating a new user with
the '/usr/sbin/useradd' script to set the users home directory
permissions to 700 rather than the Debian default of 755? I don't
understand why Debian does
-Original Message-
From: Carlos Mennens [mailto:carlosw...@gmail.com]
Sent: Wednesday, 17 March, 2010 09:50
To: Debian
Subject: Re: Change Useradd Behavior
If I change the DIR_MODE=0700 in /etc/adduser.conf, will that also be
honored when using 'useradd'?
No. Sorry, when you
On Wed, Mar 17, 2010 at 1:50 PM, Stephen Powell zlinux...@wowway.com wrote:
First of all, useradd should not be invoked directly. I suggest the
adduser frontend to useradd. Second, /etc/profile, the system-wide
bash profile, contains a setting for the default umask. Perhaps this
is what you
Carlos Mennens carlosw...@gmail.com wrote:
I have never heard this before in years or using Linux. I am not
saying you're wrong but I would just like to know why I should not use
'useradd' rather than 'adduser'. I assumed that it was just personal
preference for which you preferred to use
On Wed, 17 Mar 2010 14:02:02 -0400 (EDT), Carlos Mennens wrote:
On Wed, Mar 17, 2010 at 1:50 PM, Stephen Powell zlinux...@wowway.com wrote:
First of all, useradd should not be invoked directly. I suggest the
adduser frontend to useradd. Second, /etc/profile, the system-wide
bash profile
I do not have add machine script in smb.cfg
So, I googled and found this:
/usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u
Why not try to use smbldap-useradd and smbldap-* from smbldap-tools
package?
I don't use LDAP. Those are LDAP-specific tools, right?
--
http
I have an ancient domain, originally started with Red Hat 7.x. It is
running on latest Lenny now, and works fine, except..
Now I try to add a new server into the domain.
I found out that somehow I do not have add machine script in smb.cfg
So, I googled and found this:
/usr/sbin/useradd -d
On 4.3.2010 23:32, Jari Fredriksson wrote:
I have an ancient domain, originally started with Red Hat 7.x. It is
running on latest Lenny now, and works fine, except..
Now I try to add a new server into the domain.
Never mind, I got it.
/usr/sbin/useradd -c Machine -d /var/lib/nobody -g
googled and found this:
/usr/sbin/useradd -d /var/lib/nobody -g 100 -s /bin/false -M %u
Why not try to use smbldap-useradd and smbldap-* from smbldap-tools package?
--
-
You don't know where your shadow will fall
Olá,
Existe algum lugar, tipo no skel sei lá, para quando eu for adicionar um
usuário ele já pegue um grupo pré-estabelecido(sem ter que colocar -g
group) por mim e crie seu home com o chmod tb já
pre-estabelecido?(tipo em vez de 755 ser 700)
Valeu,
Marcelo
--
To UNSUBSCRIBE, email to
Date: Thu, 22 Oct 2009 13:44:00 -0200
From: msala...@gmail.com
To: debian-user-portuguese@lists.debian.org
Subject: duvida useradd...
Olá,
Existe algum lugar, tipo no skel sei lá, para quando eu for adicionar um
usuário ele já pegue um grupo pré-estabelecido(sem ter que colocar -g
Pessoal, como faço para o comando smbldap-useradd criar automaticamente o
home dos usuários ?
--
Desde já agradeço,
+++
Flávio de Oliveira Barros
Manaus - Amazonas - Brasil
Copiar é bom!
Seja Legal
Use Software Livre
Opa,
Acredito que ira funcionar se voce adicionar a flag -d home_dir no seu
script.
http://search.cpan.org/~ghenry/Samba-LDAP-0.05/scripts/smbldap-useradd
abs
2009/4/23 Flávio Barros flaviobar...@gmail.com
Pessoal, como faço para o comando smbldap-useradd criar automaticamente o
home dos
Solteira
http://www.ieee.org/unesp-ilha
http://www.ldc.feis.unesp.br
- Mensagem original
De: Carlos Augusto Beltrame [EMAIL PROTECTED]
Para: lista debian debian-user-portuguese@lists.debian.org
Enviadas: Sábado, 24 de Fevereiro de 2007 15:58:27
Assunto: useradd
galera tem como eu criar um
Em 27/02/07, Carlos Augusto Beltrame[EMAIL PROTECTED] escreveu:
ola pessoal, achei uma coisa na net muito legal, q acho q algumas pessoas
desconheçam, o comando chpasswd, ele consegue alterar a senha d um usuario
por stdin, coisa q nao eh possivel com o passwd, uma sintaxe para script
legal
Só corrigindo: a função é crypt, não cript. :-)
Paulo de Souza Lima
Curitiba/PR
Linux User 432358
- Mensagem original
De: Wesley [EMAIL PROTECTED]
Para: lista debian debian-user-portuguese@lists.debian.org
Enviadas: Sábado, 24 de Fevereiro de 2007 20:33:52
Assunto: Re: useradd
A Senha
galera tem como eu criar um usuario pelo useradd e passar a senha dele na linh
de comando mesmo? vi no manual tem a opção -p (password) mas eh estranho, pq a
senha q vai ali tem q ser criptografada ja, algo assim, nao entendi direito o
manual, keria fazer um programinha de cadastro pela linha d
A Senha tem que ser criptografada sim
A função é a cript. Vc pode usar um pograma que ja utilize essa função
ou pode criar um em C que o faça :D
flw
Em 24/02/07, Carlos Augusto Beltrame[EMAIL PROTECTED] escreveu:
galera tem como eu criar um usuario pelo useradd e passar a senha dele na
linh
Em 24/02/07, Carlos Augusto Beltrame[EMAIL PROTECTED] escreveu:
galera tem como eu criar um usuario pelo useradd e passar a senha dele na
linh de comando mesmo? vi no manual tem a opção -p (password) mas eh
estranho, pq a senha q vai ali tem q ser criptografada ja, algo assim, nao
entendi
On 4/10/06, Matt England [EMAIL PROTECTED] wrote:
$ useradd myname
...creates an a login named myname with a home directory of /home/myname
(or whatever pathname format the system conf/template files specify).
On at least some flavor of Debian systems (I tested with Debian3.1-based
(I realize this may be a faq, but this
'useradd -m' is hard to google...)
Summary:
Is there a more-portable way to add users to a system then
useradd(8)?
Why does Debian's useradd(8) require a -m switch when other
unix/linux systems that I have seen do not?
Details:
On non-Debian systems
(My bad for sending out html-formatted text to the list...here's the
unstyled text. -Matt)
(I realize this may be a faq, but this 'useradd -m' is hard to google...)
Summary:
Is there a more-portable way to add users to a system then useradd(8)?
Why does Debian's useradd(8) require a -m switch
Matt England wrote:
(My bad for sending out html-formatted text to the list...here's the
unstyled text. -Matt)
(I realize this may be a faq, but this 'useradd -m' is hard to google...)
Summary:
Is there a more-portable way to add users to a system then useradd(8)?
Why does Debian's
Quoting Matt England [EMAIL PROTECTED]:
(I realize this may be a faq, but this 'useradd -m' is hard to google...)
Summary:
Is there a more-portable way to add users to a system then useradd(8)?
Why does Debian's useradd(8) require a -m switch when other unix/linux
systems that I have seen do
Am 2006-03-21 17:21:41, schrieb Joachim Protze:
oder mit mkpasswd aus dem whois Paket. Keine Ahnung, was das dort drin
macht?
echo streng geheimes passwort | mkpasswd -H md5 -s
^
Sollte GROSS geschreiben
Hello,
Debian unstable useradd (shadow-4.0.15) doesn't do chown after
creating a user's home (-m option). I've found in the shadow source
package a patch with missing chown(...) line.
So... what do you think? Have anyone encountered the same problem?
-- Dalibor Straka
--
To UNSUBSCRIBE
On Tue, 21 Mar 2006 20:44:33 +0100, Wolfgang Jeltsch
[EMAIL PROTECTED] wrote:
Du solltest dein Passwort mit MD5 und nicht mit crypt verschlüsseln.
crypt kann MD5. manpage lesen bildet.
Grüße
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber
Am Mittwoch, 22. März 2006 14:05 schrieb Marc Haber:
On Tue, 21 Mar 2006 20:44:33 +0100, Wolfgang Jeltsch
[EMAIL PROTECTED] wrote:
Du solltest dein Passwort mit MD5 und nicht mit crypt verschlüsseln.
crypt kann MD5. manpage lesen bildet.
Grüße
Marc
Hmm, ich meinte mal so etwas gelesen zu
Beispiel für Perl:
perl -e 'print crypt(streng geheims passwort,aa),\n'
Danke. So habe ich es gemacht.
--
cu
Roland Kruggel mailto: [EMAIL PROTECTED]
System: Intel 3.2Ghz, Debian etch, 2.6.15, KDE 3.4
Hi Roland:
useradd kennt den Parameter -p. Hiermit kann ich beim anlegen des
Users gleich das passwort vergeben. Man sagt:
-p, --password PASSWORD
The encrypted password, as returned by crypt(3).
Wie sieht dieses Passwort aus? Wo bekomme ich crypt her? MAn crypt
bezieht sich nur
Hallo Liste,
useradd kennt den Parameter -p. Hiermit kann ich beim anlegen des
Users gleich das passwort vergeben. Man sagt:
-p, --password PASSWORD
The encrypted password, as returned by crypt(3).
Wie sieht dieses Passwort aus? Wo bekomme ich crypt her? MAn crypt
bezieht sich nur auf
Rene Kray schrieb:
Beispiel für Perl:
perl -e 'print crypt(streng geheims passwort,aa),\n'
cu René
oder mit mkpasswd aus dem whois Paket. Keine Ahnung, was das dort drin
macht?
echo streng geheimes passwort | mkpasswd -H md5 -s
Grüße Joachim
On Tuesday 21 March 2006 16:34, Roland M. Kruggel wrote:
Wie sieht dieses Passwort aus? Wo bekomme ich crypt her? MAn crypt
bezieht sich nur auf eine C library Funktion mit dem hinweis das sie
nicht exportiert werden darf.
#!/usr/bin/perl
use strict;
use warnings;
my $crypt = $ARGV[0];
print
* Joachim Protze [EMAIL PROTECTED] schrieb:
snip
oder mit mkpasswd aus dem whois Paket.
schon interessant, in welchen Paketen sich mancherlei tools
wiederfinden ...
cu
--
-
Enrico Weigelt== metux IT service
Hallo Roland,
Roland M. Kruggel, 21.03.2006 (d.m.y):
useradd kennt den Parameter -p. Hiermit kann ich beim anlegen des
Users gleich das passwort vergeben. Man sagt:
-p, --password PASSWORD
The encrypted password, as returned by crypt(3).
Wie sieht dieses Passwort aus? Wo bekomme
On Tuesday 21 March 2006 16:51, Marc Deichmann wrote:
#!/usr/bin/perl
use strict;
use warnings;
Ups, Fehler, so sieht das aus:
my $crypt = create_passwd($ARGV[0]);
print $crypt.\n;
Marc
--
GREAT MOMENTS IN HISTORY (#7): April 2, 1751
Issac Newton becomes discouraged when he falls up a
Am Dienstag, 21. März 2006 16:34 schrieb Roland M. Kruggel:
Hallo Liste,
useradd kennt den Parameter -p. Hiermit kann ich beim anlegen des
Users gleich das passwort vergeben. Man sagt:
-p, --password PASSWORD
The encrypted password, as returned by crypt(3).
Wie sieht dieses
Carlos Alberto escribió:
pessoal, estou fazendo um script no debian, porém o comando useradd no
debian não cria sua pasta no /home nem sua conta de mail no /var/mail, a
configuração default no arquivo /etc/defaults/useradd não funciona?!
Como faço?
Cria pasta no /home sim, basta usar
Bruno de Oliveira Schneider escribió:
Useradd é o comando genérico, que o único que faze é adicionar o usuário
ao arquivo /etc/passwd. Use o comando adduser, que sim faze o que você
procura.
O que seria um comando genérico?
Como eu disse antes, o useradd faz mais do que simplesmente adicionar
pessoal, estou fazendo um script no debian, porém o comando useradd no debian não cria sua pasta no /homenemsua conta de mail no /var/mail, a configuraçãodefault no arquivo/etc/defaults/useradd não funciona?! Como faço?
-- Nosso maior inimigo é a nossa própria ignorância.
Carlos Alberto escribió:
pessoal, estou fazendo um script no debian, porém o comando useradd no
debian não cria sua pasta no /home nem sua conta de mail no /var/mail, a
configuração default no arquivo /etc/defaults/useradd não funciona?!
Como faço?
Useradd é o comando genérico, que o único
Hi Andreas,
Am 2005-09-17 10:18:17, schrieb Andreas Pakulat:
Das war ein Gedaechtnisfehler meinerseits, ich meinte mcrypt in dem
Zitat gelesen zu haben, aber es war ja nur crypt.
Nur gibt es crypt nicht mehr sondern nur noch seinen Nachfolger mcrypt.
Andreas
Greetings
Michelle
--
On 17.09.05 00:18:16, Hans-Georg Bork wrote:
Moin Andreas,
On Sat, Sep 17, 2005 at 12:02:25AM +0200, Andreas Pakulat wrote:
On 16.09.05 23:42:38, Rene Sauerwein wrote:
Useradd will ein verschlüsseltes Passwort.
Und das heißt, dass ich das Passwort bereits verschlüsselt eingeben
Hallo,
mir ist aufgefallen, dass bei mir, wenn ich ein User per
useradd anlege, das Passwort unverschlüsselt in /etc/passwd steht
Wenn ich den User allerdings mit adduser anlege, steht es
verschlüsselt drinen.
Adduser lässt sich aber wiederum weniger genau einstellen.
Gibt es
Hi!
* Rene Sauerwein [EMAIL PROTECTED] [050916 23:07]:
Wenn ich den User allerdings mit adduser anlege, steht es verschlüsselt
drinen.
Klar, so isses auch gedacht. Aus man useradd:
=
-p passwd
The encrypted password, as returned by crypt(3). The
default
Klar, so isses auch gedacht. Aus man useradd:
-p passwd
The encrypted password, as returned by crypt(3). The
default is to disable the
account.
Bei mir kommt dies in der man gar nicht so vor.
Aber klar, ich legte den User doch so an
Beispiel: useradd -p
Rene Sauerwein schrieb:
Beispiel: useradd -p hallo user
Dann steht hallo unverschlüsselt in /etc/passwd
Aber wenn ich den User user mit adduser anlege, dann ist das Passwort
verschlüsselt..
Useradd will ein verschlüsseltes Passwort.
Ciao
Walter
--
Haeufig gestellte Fragen und Antworten
Useradd will ein verschlüsseltes Passwort.
Und das heißt, dass ich das Passwort bereits verschlüsselt eingeben muss? -p
verschlüsseltes passwd ?
Und wie generiere ich es am Besten als verschlüsseltes?
Gruß Rene
On 16.09.05 23:26:37, Rene Sauerwein wrote:
Klar, so isses auch gedacht. Aus man useradd:
-p passwd
The encrypted password, as returned by crypt(3). The
default is to disable the
account.
Bei mir kommt dies in der man gar nicht so vor.
Aber klar
On 16.09.05 23:42:38, Rene Sauerwein wrote:
Useradd will ein verschlüsseltes Passwort.
Und das heißt, dass ich das Passwort bereits verschlüsselt eingeben muss? -p
verschlüsseltes passwd ?
Und wie generiere ich es am Besten als verschlüsseltes?
Das steht auch in dem entsprechenden
Hallo Rene!
On Fri, 16 Sep 2005 23:42:38 +0200 Rene Sauerwein [EMAIL PROTECTED] wrote:
Useradd will ein verschlüsseltes Passwort.
Und das heißt, dass ich das Passwort bereits verschlüsselt eingeben muss? -p
verschlüsseltes passwd ?
Und wie generiere ich es am Besten als verschlüsseltes?
Am
Hallo,
Am besten nimmst du adduser.
Nein will ich nicht, adduser lässt mich keine Gruppe festlegen und keine
Shell und gar nichts.
Adduser will nur ein Username und Passwort und macht den Rest automatisch.
Und bei Useradd lässt sich eben alles genau festlegen.
Eine Art useradd, was aber mit
On Fri, Sep 16, 2005 at 11:42:38PM +0200, Rene Sauerwein wrote:
Useradd will ein verschlüsseltes Passwort.
Und das heißt, dass ich das Passwort bereits verschlüsselt eingeben muss? -p
verschlüsseltes passwd ?
Und wie generiere ich es am Besten als verschlüsseltes?
z.B. mit makepasswd
On Fri, Sep 16, 2005 at 11:26:37PM +0200, Rene Sauerwein wrote:
Klar, so isses auch gedacht. Aus man useradd:
-p passwd
The encrypted password, as returned by crypt(3). The
default is to disable the
account.
Bei mir kommt dies in der man gar nicht
Hallo,
Was genau steht denn in _Deiner_ Manpage darueber? Ich finde obiges in der
manpage auf verschiedensten Systemen ...
Gerne zeige ich dir ein Ausschnitt von man useradd
Gruß Rene
Aber Problem ist ja mittlerweile gelöst ;)
SYNOPSIS
useradd [-c comment] [-d home_dir
Hallo,
Was genau steht denn in _Deiner_ Manpage darueber? Ich finde obiges in
der manpage auf verschiedensten Systemen ...
Tut mir leid, da handelte es sich um ein Missverständnis, übersah more und
blätterte nicht nach unten
Gruß Rene
Moin Andreas,
On Sat, Sep 17, 2005 at 12:02:25AM +0200, Andreas Pakulat wrote:
On 16.09.05 23:42:38, Rene Sauerwein wrote:
Useradd will ein verschlüsseltes Passwort.
Und das heißt, dass ich das Passwort bereits verschlüsselt eingeben muss? -p
verschlüsseltes passwd ?
Und wie
Moin Rene,
On Sat, 2005-09-17 at 00:12 +0200, Rene Sauerwein wrote:
Hallo,
Am besten nimmst du adduser.
Nein will ich nicht, adduser lässt mich keine Gruppe festlegen und keine
Shell und gar nichts.
Adduser will nur ein Username und Passwort und macht den Rest automatisch.
sag mal, was
mit was
anderem.
Aber da ich mich an Useradd gewöhnte werde ich die Methode bevorzugen:
Zuerst User anlegen
Danach: passwd user
Gruß Rene
Am Sat, 17 Sep 2005 00:20:09 +0200 schrieb Rene Sauerwein:
Adduser will nur ein Username und Passwort und macht den Rest
automatisch. Und bei Useradd lässt sich eben alles genau festlegen.
schonmal adduser --help eingetippt?
adduser [--home DIR] [--shell SHELL] [--no-create-home] [--uid ID
ok c'est parfait!
Pil Poil ce que je cherchais.
merci
nono
signature.asc
Description: Digital signature
1 - 100 of 172 matches
Mail list logo
