What are the 1000, 10001.. user accounts?

  • Hi all, I've just done a fresh install of OMV 3. I noticed that there are several user accounts (1000, 1001..). I didn't have these in OMV2; I only had those accounts that I created.


    Did OMV3 create these accounts? As you can see from the attached picture, permissions have already been set for them by someone/something else. Thoughts?

  • Here is the output (sidenote: is there anything in this that shouldn't be shared publicly?)


    NAS OMV 3.0.59 Rig: DFI Lanparty nForce4 SLI-DR | Opteron 165 Dual Core (no overclock) | 4GB Corsair Non-ECC DDR400 RAM | OMV3: 1x100GB IDE | Data: 2x 250GB WD 7200rpm, 2x 3TB WD Red, 1x 4TB Samsung 5400rpm

    • Offizieller Beitrag

    is there anything in this that shouldn't be shared publicly?

    It is safe to share. You wouldn't want to share /etc/shadow which is where the encrypted passwords for those users live.


    Strange. Do you have the ldap plugin installed/configured? You don't even have a user with most of the IDs in your pic.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I don't have LDAP installed, no. I did a fresh install of OMV3 and merely setup one user. I agree, I was surprised to find the 1000..1006, 995 users too.. Should I delete them?

    NAS OMV 3.0.59 Rig: DFI Lanparty nForce4 SLI-DR | Opteron 165 Dual Core (no overclock) | 4GB Corsair Non-ECC DDR400 RAM | OMV3: 1x100GB IDE | Data: 2x 250GB WD 7200rpm, 2x 3TB WD Red, 1x 4TB Samsung 5400rpm

    • Offizieller Beitrag

    Should I delete them?

    You can try but they don't exist in the passwd file. So, you shouldn't be able to delete them. I would try deleting 1006 first since it is not in the passwd file.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I see what you mean. Yes, these users don't exist on the users tab; I only see them when managing ACL for a share.


    Is this a security risk? I'm not sure what to do with them..

    NAS OMV 3.0.59 Rig: DFI Lanparty nForce4 SLI-DR | Opteron 165 Dual Core (no overclock) | 4GB Corsair Non-ECC DDR400 RAM | OMV3: 1x100GB IDE | Data: 2x 250GB WD 7200rpm, 2x 3TB WD Red, 1x 4TB Samsung 5400rpm

  • Just a thought - could these users be related to my reinstallation?


    I setup several users while using OMV2, created several shares for these users, upgraded to OMV3. Had issues with SickRage. Reinstalled OMV3, and then setup only 2 users (many of the users that I previously setup were not recreated).

    NAS OMV 3.0.59 Rig: DFI Lanparty nForce4 SLI-DR | Opteron 165 Dual Core (no overclock) | 4GB Corsair Non-ECC DDR400 RAM | OMV3: 1x100GB IDE | Data: 2x 250GB WD 7200rpm, 2x 3TB WD Red, 1x 4TB Samsung 5400rpm

    • Offizieller Beitrag

    Is this a security risk? I'm not sure what to do with them..

    I don't think so. Need to figure out why they are there. I never use ACLs so I wouldn't have noticed this bug (if it is one).

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    could these users be related to my reinstallation?

    Maybe? What is the output (run as root) of: grep 1006 /etc/openmediavault/config.xml

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • There is no output for 1006.


    For 1001:


    Code
    root@NAS:/# grep 1001 /etc/openmediavault/config.xml
              <priority2>1001</priority2>
              <priority2>1001</priority2>

    NAS OMV 3.0.59 Rig: DFI Lanparty nForce4 SLI-DR | Opteron 165 Dual Core (no overclock) | 4GB Corsair Non-ECC DDR400 RAM | OMV3: 1x100GB IDE | Data: 2x 250GB WD 7200rpm, 2x 3TB WD Red, 1x 4TB Samsung 5400rpm

    • Offizieller Beitrag

    Maybe @votdev would have a better idea why the privileges grid is showing user and group IDs that don't exist?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.1.4 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • These permissions appear to be specific to the share folder. To work around the issue, it was necessary to move data from folder A to folder B. Delete folder A. Recreate folder A. Then move data from folder B to folder A.


    I performed the above for two of the five share-folders that I migrated from OMV2. For the remaining three, I used the reset-perms plugin; this plugin works very well.


    New folders or shares that are created are not affected, so I presume that the above issue is related to the OMV2 to 3 upgrade (but easily fixable with reset-perms).

    NAS OMV 3.0.59 Rig: DFI Lanparty nForce4 SLI-DR | Opteron 165 Dual Core (no overclock) | 4GB Corsair Non-ECC DDR400 RAM | OMV3: 1x100GB IDE | Data: 2x 250GB WD 7200rpm, 2x 3TB WD Red, 1x 4TB Samsung 5400rpm

  • Thanks for this. Your thoughts make sense. I resolved the issue by using the 'reset perms' plugin on those folders I was sharing on a previous version of OMV.

    NAS OMV 3.0.59 Rig: DFI Lanparty nForce4 SLI-DR | Opteron 165 Dual Core (no overclock) | 4GB Corsair Non-ECC DDR400 RAM | OMV3: 1x100GB IDE | Data: 2x 250GB WD 7200rpm, 2x 3TB WD Red, 1x 4TB Samsung 5400rpm

  • I have to pick up this oder topic because I expirience the same issue, but not after an upgrade from OMV.


    My OMV3 is running for quite long, I changed permissions for a shared folder and saw under all ACL user 1003 with read-permissions to all of my shared folders. The user 1003 does not show up under unsers tab.


    Code
    cat /etc/passwd

    does not list the 1003 user


    security issue?

    Chaos is found in greatest abundance wherever order is being sought.
    It always defeats order, because it is better organized.
    Terry Pratchett

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!