You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@vcl.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/01 17:06:00 UTC

[jira] [Commented] (VCL-1081) UID conflict for admin user

    [ https://issues.apache.org/jira/browse/VCL-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758492#comment-16758492 ] 

ASF subversion and git services commented on VCL-1081:
------------------------------------------------------

Commit 5abdb11879bc7d75ea927aa648e2bf9b77ccedfc in vcl's branch refs/heads/develop from Josh Thompson
[ https://gitbox.apache.org/repos/asf?p=vcl.git;h=5abdb11 ]

VCL-1081 - UID conflict for admin user

vcl.sql: changed UID for admin user to NULL to prevent conflicts with existing UIDs on systems


> UID conflict for admin user
> ---------------------------
>
>                 Key: VCL-1081
>                 URL: https://issues.apache.org/jira/browse/VCL-1081
>             Project: VCL
>          Issue Type: Bug
>          Components: database, vcld (backend)
>            Reporter: Josh Thompson
>            Priority: Major
>             Fix For: 2.5.1
>
>
> A user reported on the user@ list that he was having a conflict with the admin user and the syslog user on an Ubuntu system because the syslog user had a uid of 101, which is what is set for the admin user. We should either set uid for the admin user to NULL, set it to a higher value, or have vcld check for a conflict before adding the user and either allow the OS to set the UID for the user or fail the reservation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)