Description of Problem:
All env-variables of jobs started by at-3.1.8-18 get empty values. The
man-page says they are retained.
The at-3.1.8-env.patch seems to be responsibly. There the last hunk
- fwrite(*atenv, sizeof(char), eqp - *atenv - 1, fp);
+ fwrite(*atenv, sizeof(char), eqp - *atenv, fp);
should be removed. Else entries like
| <var>=<values>; export <var>=
will be created.
| <var>=<values>; export <var>
would be correct.
Steps to Reproduce:
1. echo 'test' | at now+5min
2. at -c <number of the job>
PWD=/home/ensc; export PWD=
http_proxy=http://www-cache:3128/; export http_proxy=
PWD=/home/ensc; export PWD
http_proxy=http://www-cache:3128/; export http_proxy
$ rpm -q at
It's a serious bug making `at' unusable. Therefore increasing importance...
Created attachment 24010 [details]
This patch should replace the original at-3.1.8-env.patch
This defect should be fixed ASAP, Crutcher.
Sorry, my suggested patch was erroneous and reopens perhaps the door to a local
attack (have overseen that at is SUID and user can give a manipulated env like
Created attachment 24287 [details]
Should fix it finally