Date: Sun, 5 Feb 2012 23:18:59 GMT From: Garrett Cooper <yanegomi@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: bin/164808: system crontab doesn't support usernames with spaces in them Message-ID: <201202052318.q15NIxHc030756@red.freebsd.org> Resent-Message-ID: <201202052320.q15NK8hp017101@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 164808 >Category: bin >Synopsis: system crontab doesn't support usernames with spaces in them >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 05 23:20:08 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Garrett Cooper >Release: 9.0-STABLE >Organization: iXsystems, Inc. >Environment: FreeBSD bayonetta.local 9.0-STABLE FreeBSD 9.0-STABLE #4 r230371M: Thu Jan 19 23:55:38 PST 2012 gcooper@bayonetta.local:/usr/obj/store/freebsd/stable/9/sys/BAYONETTA amd64 >Description: Doing some testing for FreeNAS, I discovered that the system crontab user field isn't properly tokenized, such that usernames with spaces in them are permitted. This isn't standard, but it's an issue with folks who are Windows users attempting to do tasks which need to be driven via the system crontab. Per user crontabs worked however. >How-To-Repeat: 1. Create a username with a space in it on a Windows domain (example: "AD\foo bar", where AD is the subdomain and the username is: "foo bar"). 2. Install FreeNAS 8.0.3 on a machine. 3. Join the FreeNAS box to the domain. 4. Create a cronjob with "AD\foo bar" that executes the command "echo hello > /tmp/iwuzhere". 5. "cat /tmp/iwuzhere" after the job has run [theoretically]. If successful, it should exist and say "hello". >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202052318.q15NIxHc030756>