[krbdev.mit.edu #2883] 64-bit time_t issues

[Ken Raeburn via RT]

On Mar 15, 2005, at 01:06, Jeffrey Altman via RT wrote:
> Here is a list of all 64-bit related warnings generated by the Windows
> .NET 2005 compiler.
>
>
> c:\src\kerberos\mit-cvs\krb5- 
> head\src\lib\krb5\asn.1\asn1_k_decode.c(288)
> : warning C4244: '=' : conversion from 'time_t' to 'krb5_timestamp',
> possible loss of data

Most of the krb5_timestamp issues should probably be dealt with by  
making krb5_timestamp 64 bits on 64-bit Windows, as we were discussing.  
  Though there might be interesting issues if 64-bit Windows supports  
32-bit Windows software, and krb5_timestamp is used in any IPC (CCAPI?)  
or file formats (ccache, keytab).  Which, actually, it appears to be.   
So maybe this isn't quite so simple after all.

> These are not time_t issues but still:
>
> c:\src\kerberos\mit-cvs\krb5-head\src\lib\gssapi\krb5\k5seal.c(246) :
> warning C4244: 'function' : conversion from 'gssint_uint64' to
> 'krb5_ui_4', possible loss of data

All of these are in code implementing the original GSSAPI mech with  
32-bit sequence numbers.  So maybe there should be an "assert(seqnum <=  
0xffffffff)" but otherwise it's okay.