time_t (such as that returned by gettime() and friends) are always
supposed to be in GMT, unaffected by timezone settings. That's
something that a lot of people end up misconfiguring on their systems.
On 1/27/06, Joe Gluck [EMAIL PROTECTED] wrote:
Hi all,
I have a certificate with dates
In which library is that gettime() function in? I did not find it.
(I did not find it in any C library)
Joe
On 1/28/06, Kyle Hamilton [EMAIL PROTECTED] wrote:
time_t (such as that returned by gettime() and friends) are always
supposed to be in GMT, unaffected by timezone settings. That's
On Sat, Jan 28, 2006 at 05:38:18AM -0800, Joe Gluck wrote:
In which library is that gettime() function in? I did not find it.
(I did not find it in any C library)
He probably meant time(2), but you could also use gettimeofday(2).
Kurt
Thank you, yes, that was what I meant. (gettimeofday() was
specifically what I was thinking of, but time() also works. Either
way, it's supposed to be GMT, not localized. Any localizations are
applied to the number you get, unless the library itself does it.)
-Kyle
On 1/28/06, Kurt Roeckx
On Fri, Jan 27, 2006, Joe Gluck wrote:
Does some one have any idea about this, it looks like it fell out
through the night.
The comment in there explains fairly well why it is surrounded by #if 0
Steve.
--
Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage
OpenSSL project core
Thank you for all tour replies but the gettimeofday I already use, but
it was not what I was asking in the original message.
What I asked is how can I get the ASN1_integer into a time_t to be
able to compare it with the current GMT time (which i can get with
some system functions, on linux
On Sat, Jan 28, 2006, Joe Gluck wrote:
Thank you for all tour replies but the gettimeofday I already use, but
it was not what I was asking in the original message.
What I asked is how can I get the ASN1_integer into a time_t to be
able to compare it with the current GMT time (which i can
My mistake it was ASN1_TIME that is correct.
But any way, I don't see a reason why I should not be able to convert
it, if I don't care for milliseconds, time_t can represent times for
up to 2038, so It should be ok to convert it to the time_t.
Any ideas, the ASN1_cmp_time does much more than
On Sat, Jan 28, 2006, Joe Gluck wrote:
My mistake it was ASN1_TIME that is correct.
But any way, I don't see a reason why I should not be able to convert
it, if I don't care for milliseconds, time_t can represent times for
up to 2038, so It should be ok to convert it to the time_t.
An
From the Linux gnu libc timegm(3) manpage:
For a portable version of timegm(), set the TZ environment variable to
UTC, call mktime() and restore the value of TZ.
-Kyle H
On 1/28/06, Dr. Stephen Henson [EMAIL PROTECTED] wrote:
On Sat, Jan 28, 2006, Joe Gluck wrote:
My mistake it was
I can't change the TZ because it will affect the entire system and it
is a production system running on client sites, so I can't just change
the TZ.
and the mktime wil return it in time_t but after converting it to local time.
(The only thing that I may be can do, is load the times from the cert
Thanks, I did not know that.
On 1/28/06, Kyle Hamilton [EMAIL PROTECTED] wrote:
TZ is an environment variable. Each process gets its own environment
that it can change at will, that is sandboxed from every other
environment. This environment is copied to child processes at fork(),
though an
12 matches
Mail list logo
