Beiträge von 618116

    I did call it a bug allowing it.

    It seems there is some misunderstands. I am not claiming OMV support digit username. If developer decided not to support it, I am OK with it.

    The point I call this situation bug is UI and internal behavior is not matched. As you agreed, unsupported user behavior should be stopped at UI. So In this case, I'd call it is UI bug rather than implementation bug.

    Just because it worked in previous versions doesn't mean it the correct thing to do. The "bug" was allowing it in the first place. Part of allowing it was "fixed".

    I don't use my forum username(s) on any Linux systems.

    I can't see the point. As mentioned in Github, pure digit username is not prohibited in Debian nor OMV itself. It might be unrecommended, but nothing "incorrect". If OMV implementation cannot support it, it should be stopped at UI input. In current situation, the digit username is allowed by UI but not work correctly. It can be called "bug".

    I don't use my forum username(s) on any Linux systems.

    Well, you don't, I did.

    While you can use a number (as Volker mentioned on github), it doesn't make any sense to since most Linux user commands treat a real number as the user id instead of the username. I think the web interface should prevent this from being entered. Why do you have to use a number with no letters??

    As you can see my name, I have used this number as my username for a few years.

    Also older version of OMV recognized this number username, this behavior is changed in an update.

    User info can be get by getent passwd.

    Zitat

    618116:x:1002:100:testcomment:/srv/dev-disk-by-label-DATA/HOME/618116:/bin/bash

    (UID is changed for test)


    However, omv-rpc -u admin 'UserMgmt' 'enumerateUsers' cannot get the user info.


    It seems some function of rpc is not working correctly.

    Using OMV 5 in RB4.


    I have a user can used to smb and ssh, but I cannot access to the user in web GUI.


    Here is output from "cat /etc/passwd".

    618116 is the user have problem.


    any suggestion?