[MSHARED-1446] Add docs about repro build output timestamp boundaries

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-archiver-3.6.2
• Fix Version/s: maven-archiver-4.0.0, maven-archiver-3.6.3, maven-archiver-4.0.0-beta-2
• Component/s: maven-archiver
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 15/Oct/24 07:09
• Updated: 22/Oct/24 15:12
• Resolved: 22/Oct/24 15:12

Description

In MSHARED-1067 the boundaries have been introduced, but never documented by they actually exist. Reason: MS-DOS time limitation for 2+2 bytes starting from 1980. See ZIP note:

4.4.6 date and time fields: (2 bytes each)

The date and time are encoded in standard MS-DOS format.
If input came from standard input, the date and time are
those at which compression was started for this data.
If encrypting the central directory and general purpose bit
flag 13 is set indicating masking, the value stored in the
Local Header will be zero. MS-DOS time format is different
from more commonly used computer time formats such as
UTC. For example, MS-DOS uses year values relative to 1980
and 2 second precision.

Issue Links

• is caused by: MSHARED-1445 Unix timestamps since the epoch are not subject to the boundary checks
• links to: Docs from Microsoft
• links to: GitHub Pull Request #73
• links to: libarchive ZIP date/time conversion
• links to: Yet another ref