mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Oliver.Graute@neuhaus.de
To: ptxdist@pengutronix.de
Subject: [ptxdist] Warning UID is greater than 99
Date: Thu, 10 Sep 2015 16:23:37 +0200	[thread overview]
Message-ID: <OF6F63ABBE.EB7BD6E0-ONC1257EBC.004B2F20-C1257EBC.004F1256@neuhaus.de> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 955 bytes --]


Hello,

in my rule file I create some directorys with special UID and GID  for a
sftp user.

ifdef PTXCONF_DNT3202STARTUP_CREATE_SFTP_DIR
         @$(call install_copy, dnt3202startup, 0, 0, 0755,       /sftp/)
         @$(call install_copy, dnt3202startup, 0, 0,
0755,       /sftp/sftp_user/)
         @$(call install_copy, dnt3202startup, 1001, 1000,
0755, /sftp/sftp_user/incoming)
         @$(call install_copy, dnt3202startup, 1001, 1000,
0755, /sftp/sftp_user/outgoing)
endif

this is working fine for me on the target. But today I noticed this Warning
in ptxdist log:

*** Warning: The following files have a UID greater than 99.
You probably want to chown these to a system user:
drwxr-xr-x 2 lgl mgo 4096 Sep 10 15:40 ./home/shell_user
drwxr-xr-x 2 lgl mgo 4096 Sep 10 15:40 ./sftp/sftp_user/incoming
drwxr-xr-x 2 lgl mgo 4096 Sep 10 15:40 ./sftp/sftp_user/outgoing

is this something to worry about? or can I ignore that?

Best regards,

Oliver

[-- Attachment #1.1.2: Type: text/html, Size: 1080 bytes --]

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2446 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2015-09-10 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 14:23 Oliver.Graute [this message]
2015-09-10 15:04 ` Marc Kleine-Budde
2015-09-13  3:58   ` Enrico Weigelt, metux IT consult
2015-09-13 13:01     ` Marc Kleine-Budde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OF6F63ABBE.EB7BD6E0-ONC1257EBC.004B2F20-C1257EBC.004F1256@neuhaus.de \
    --to=oliver.graute@neuhaus.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox