Risk Assessment Summary
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
ENV30-C | Low | Probable | Medium | P4 | L3 |
ENV31-C | Low | Probable | Medium | P4 | L3 |
ENV32-C | Medium | Likely | Medium | P12 | L1 |
ENV33-C | High | Probable | Medium | P12 | L1 |
ENV34-C | Low | Probable | Medium | P4 | L3 |
1 Comment
Casey Klimasauskas
Do NOT modify the TZ enviornment as part of a hack to convert date/time from one time zone to another.
I spent several days tracking down a bug in a production environment with a multi-threaded application in which conversion between time zones was done by setting the TZ environment variable to one time zone, getting local time, then changing to another time zone to get an ascii string to store the information in a database. Other portions of the code accessed the time functions to find the current time (assumed) local time. Depending on race conditions, this occasionally resulted in incorrect times. This is a published hack that should NOT be used. Use Boost or similar library instead.