Project

General

Profile

Actions

Bug #4855

closed

GroupManager stops working with LDAP after (something?), /usr/sbin/pw exiting w/error

Added by Overand IRC-Priv almost 9 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
User Manager / Privileges
Target version:
-
Start date:
07/19/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.3
Affected Architecture:
amd64

Description

I'm not sure I can reproduce this issue, but the system is still up.

I'd renamed / created/ removed / created some groups, hitting the max 16 char limit. (Fun, with LDAP). Then I noticed my users weren't showing up in the expected groups (any groups) on test.

php-fpm[59177]: /system_groupmanager.php: The command '/usr/sbin/pw groupmod pfSense Admins -g 2002 -M '' 2>&1' returned exit code '1', the output was 'pw: entry inconsistent pw: gr_copy(): Invalid argument'

pfSense 2.2.3, 64 bit (as tagged).

I'm fairly unix-and-friends saavy; I can SSH in and provide extra info if desired. (But this is a production machine; I can clone its live state, though, it's a VMWare VM).

Actions #1

Updated by Kill Bill about 7 years ago

OK, so this would seem to be caused by the space in groupname - that appears to be handled by input validation now [1] and is only allowed for remote groups which are not put to /etc/group. Can be closed.

[1] https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/system_groupmanager.php#L137

Overand IRC-Priv wrote:

Then I noticed my users weren't showing up in the expected groups (any groups) on test.

P.S. Changing anything here requires a reboot to take effect. (No comment.) - https://redmine.pfsense.org/issues/7013

Actions #2

Updated by Jim Pingle about 7 years ago

  • Status changed from New to Resolved

That does appear to be what it was. If it can still be reproduced somehow on 2.4 we can dig in more.

Actions

Also available in: Atom PDF