Sebastien Bacher wrote:
Are you making that from that only bug? Adding complexity to the system
will not prevent bugs to happen. All the versions of Ubuntu are meant to
be stable and secure and I don't think that calling edgy unsecure is a
fair statement. Using those tools require to be logged wit
On Wed, Nov 29, 2006 at 10:14:46PM -, Sebastien Bacher wrote:
> Are you making that from that only bug? Adding complexity to the system
> will not prevent bugs to happen. All the versions of Ubuntu are meant to
> be stable and secure and I don't think that calling edgy unsecure is a
> fair stat
Le mercredi 29 novembre 2006 à 20:19 +, Kurt a écrit :
> Considering this, it is really a great security risk that the admin
> tools do not check the password because if the admin user gets
> compromised, one can easily add a new user, log in as this one and do
> everything.
The admin user al
Many people running ubuntu work with only one user (which is in the
administrator's group) - and this is also the default.
Considering this, it is really a great security risk that the admin
tools do not check the password because if the admin user gets
compromised, one can easily add a new user,
Instructions by Justin Dugger solved my problem. I guess some kind of
check script should be pushed as an update of some sort, to make sure
this is solved on all systems.
Not that this matters in my case, I need to completely re-install Ubuntu
because of all the upgrade issues :(
--
Admin tools
Sorry forgot something:
Now after Rebooting I experienced, that e.g. services-admin starts without
asking permissions. Then you need to run alacarte menu editor and check the
section >System >Administration and put gksu before these commands:
gksu gdmsetup
gksu users-admin
gksu time-admin
gksu s
For me the error occured when I wanted to disable some services via
"services-admin". Accidentally I unchecked dbus. And since there was the
problem.
Fix:
Run Synaptic (should still work)
Re-Install following packages:
-gnome-system-tools
-system-tools-backend
-dbus
-libdbus-1-3
(or simply all pac
After upgrade I was bitten by https://launchpad.net/bugs/69145 as I
initially installed Breezy, in March. I have now fixed the problem by
adding "admin" by hand, but what does "admin" signify that "adm" does
not? My /etc/sudoers has "adm" and I was (and am) a member of "adm",
but that was apparant
** Summary changed:
- run action as root without prompting for a password
+ Admin tools require admin group membership
--
Admin tools require admin group membership
https://launchpad.net/bugs/59946
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
Tom,
Clearly the upgrade didn't add user "tom" to the admin group, or possibly even
create one.
Workaround:
1. run "gksudo users-admin"
2. Click manage groups
3. Click add Group
4. Put "admin" as the name of the group, and put whatever users you want to
allow to change system wide settings su
Breezy -> Dapper -> Edgy
Rebooted several times. Still not solved.
Maybe this helps. The username I'm using is 'tom' which was created
during the breezy installation. This user is in the following groups:
$ cat /etc/group |grep "tom"
adm:x:4:tom
dialout:x:20:tom,cupsys
cdrom:x:24:tom,hal,haldaem
Le mardi 31 octobre 2006 à 16:23 +, Aaron C. de Bruyn a écrit :
> Darn. I thought I had rebooted the box. It's working now.
>
> So apparently this is caused by an earlier version of Ubuntu (say
> Dapper?) and when upgrading to Edgy the admin group isn't created?
that's happening for people
Darn. I thought I had rebooted the box. It's working now.
So apparently this is caused by an earlier version of Ubuntu (say
Dapper?) and when upgrading to Edgy the admin group isn't created?
--
Admin tools require admin group membership
https://launchpad.net/bugs/59946
--
desktop-bugs mailin
13 matches
Mail list logo
