Looking at the 5.x source, it looks like Seek() was actually changed to 'dword', which is an unsigned _int64 on Windows : ). I guess I should have looked at the new source first (although it wasn't mentioned in the changes).
Great. -- gl ----- Original Message ----- From: "gl" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, February 02, 2003 1:39 AM Subject: 32bit limits? > > (Windows, 4.2 lib) > > Hi, > > I'm working on a .zip style file container, and I'd like to support large > files (> 2^32). I'm using counter mode to allow for random access > read/writing, but looking at the 4.2 stream cipher code that I'm working > with, it only allows a 32bit (unsigned long) Seek() call. > > Presumably this limit exists in the 5.x version too, so is there any way to > work around it? My first thought is to restart the encryption when I hit a > boundary (generate a new IV and write it, then continue) - that's messy > though. > > I'd prefer to modify the source to work with 'unsigned _int64' (on > Windows) - can this be done? I obviously don't want to break anything, so > I'd appreciate any advice... > -- > gl >
