Your message dated Mon, 13 Feb 2023 17:03:56 +
with message-id
and subject line Bug#1029077: fixed in debian-edu-config 2.12.29
has caused the Debian Bug report #1029077,
regarding debian-edu-config: leaks first user password in Debconf answers
to be marked as done.
This means that you claim
Source: debian-edu-config
Version: 2.12.25
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It was discovered that the password for the first user (GOSa); and root
user if using the Debian Edu installer, is not cleared from the Debconf
answers database. It is also therefore
Hi Roman,
[ roman.me...@gismap.ch, 2021-10-15 ]
> The first user changed his password and is saying, he can't log in
> anymore. How can I fix this?
If you have another trusted user, say Jane Doe, with username jdoe:
As root on the main server, run 'ldapvi -ZD '(cn=admin)&#
Hi folks,
The first user changed his password and is saying, he can't log in anymore. How can I fix this?
Kind regards,
Roman
Your message dated Thu, 29 Apr 2021 13:48:54 +
with message-id
and subject line Bug#987632: fixed in debian-edu-config 2.11.55
has caused the Debian Bug report #987632,
regarding fails to create Samba account for first user during main server
installation
to be marked as done.
This means
Package: debian-edu-config
Version: 2.11.54
Severity: normal
During main server installation information is still missing to create
the first user's Samba account. This should be done at first booot of
the main server when all required information is available via LDAP and
debconf.
Wolfgang
Dear Wolfgang Schweer
On 5/9/19 6:16 PM, Wolfgang Schweer wrote:
Hi hoxp18,
On Thu, May 09, 2019 at 05:55:17PM +0900, hoxp18 wrote:
I want to ask a question about "first user".
In the manual,
* It is a "first" user account in the main server installation.
Yes, that&#x
Hi hoxp18,
On Thu, May 09, 2019 at 05:55:17PM +0900, hoxp18 wrote:
> I want to ask a question about "first user".
>
> In the manual,
>
> * It is a "first" user account in the main server installation.
Yes, that's the user account you are also prompt
To: Debian Edu team,
Greeting.
I want to ask a question about "first user".
In the manual,
* It is a "first" user account in the main server installation.
* "first user" is special account; not "root" itself, though sudoable.
* "first user"
On Thu, Oct 15, 2015 at 08:27:36AM +, Mike Gabriel wrote:
> Ok. I get that. The balance here is: simple for maintainers and simple for
> first-time users/admins.
Yes. Hard to find the right one.
> >Also, avoiding changes to the initial
> >LDAP data base would make upgrading easier.
>
> I al
Hi Wolfgang,
On Mi 14 Okt 2015 17:32:05 CEST, Wolfgang Schweer wrote:
On Wed, Oct 14, 2015 at 02:24:24PM +, Mike Gabriel wrote:
I have just committed a fix for this, unfortunately ignoring earlier
discussions and preferences.
The chosen path now adds a group "printer-admins" to LDAP when
On Wed, Oct 14, 2015 at 02:24:24PM +, Mike Gabriel wrote:
> I have just committed a fix for this, unfortunately ignoring earlier
> discussions and preferences.
>
> The chosen path now adds a group "printer-admins" to LDAP when bootstrapping
> and make the initial user a member of that group.
>
Control: forcemerge #793678 -1
Hi all,
On Sa 27 Sep 2014 15:57:23 CEST, Wolfgang Schweer wrote:
On Sat, Sep 27, 2014 at 01:29:15PM +0200, Giorgio Pioda wrote:
> > administration.
>
> I had a closer look, and one fix would be to tell cups to treat all
> members of one of the groups granting p
Hi,
On Samstag, 27. September 2014, Wolfgang Schweer wrote:
> My experience at school tells me to propose:
>
> Use the jradmins group. This way not all teachers are automatically
> allowed to manage printers. And there would be the possibility to add
> skilled and reliable students to the jradmin
On Sat, Sep 27, 2014 at 01:29:15PM +0200, Giorgio Pioda wrote:
> > > administration.
> >
> > I had a closer look, and one fix would be to tell cups to treat all
> > members of one of the groups granting privileges as a system user.
> > This can be done by adding the to the list of privileged group
Hi
On Fri, Sep 26, 2014 at 11:19:24PM +0200, Petter Reinholdtsen wrote:
> [Petter Reinholdtsen]
> > We should look for a way to get the same effect for CUPS
> > administration.
>
> I had a closer look, and one fix would be to tell cups to treat all
> members of one of the groups granting privile
[Petter Reinholdtsen]
> We should look for a way to get the same effect for CUPS
> administration.
I had a closer look, and one fix would be to tell cups to treat all
members of one of the groups granting privileges as a system user.
This can be done by adding the to the list of privileged groups
[David Prévot]
> In order to be able to actually administrate the printers (CUPS),
> the first user has to be added to the lpadmin group. It would be
> nice if that was done by default (on tjener, where CUPS is
> installed).
Note, the first user exist only in LDAP and Kerberos, while
Source: debian-edu-config
Severity: wishlist
Hi,
In order to be able to actually administrate the printers (CUPS), the
first user has to be added to the lpadmin group. It would be nice if
that was done by default (on tjener, where CUPS is installed).
One alternative would be to use the root
On Tue, Aug 20, 2013 at 12:41:56PM +0200, Wolfgang Schweer wrote:
> On Tue, Aug 20, 2013 at 12:27:47PM +0200, Giorgio Pioda wrote:
> >
> > changing the first user passwd is just changing any other user passwd in
> > gosa
> > or does it affect also gosa.conf and/or
On Tue, Aug 20, 2013 at 12:27:47PM +0200, Giorgio Pioda wrote:
>
> changing the first user passwd is just changing any other user passwd in gosa
> or does it affect also gosa.conf and/or other files/hashes?
It shoudn't affect anything else. (You'll only have to change the
[Giorgio Pioda]
> Hi,
>
> changing the first user passwd is just changing any other user
> passwd in gosa or does it affect also gosa.conf and/or other
> files/hashes?
It is just as any other user in that regard. It is only special
because it is member of a privilaged group, an
Hi,
changing the first user passwd is just changing any other user passwd in gosa
or does it affect also gosa.conf and/or other files/hashes?
Regards
--
Giorgio Pioda - Sysadmin SPSE-Tenero
Cell +41 79 629 20 63
Uff. +41 91 735 62 48
--
To UNSUBSCRIBE, email to debian-edu-requ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 8 Sep 2005 14:40:35 +0200
Klaus Ade Johnstad <[EMAIL PROTECTED]> wrote:
> torsdag 8. september 2005, 14:12, skrev James Yale:
> > The solution would seem to be to kill the esd server on logout, but
> > there is no way that the thin client know
torsdag 8. september 2005, 14:12, skrev James Yale:
> The solution would seem to be to kill the esd server on logout, but
> there is no way that the thin client knows when a user logs out (it's
> all fowarded X?) so there isn't any part of the logout script that
> can be editted to kill the esd dae
Hi,
I'm not sure if this has been mentioned before, I couldn't find it in
the archives but I'm sure I read something about it.
The problem I'm having is on the thin clients I've setup (using the
2.6.9-ltsp-3 kernel), the first user (say, user01) logs in and gets
sound
26 matches
Mail list logo
