[
https://issues.apache.org/jira/browse/MSHARED-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889487#comment-17889487
]
Michael Osipov commented on MSHARED-1445:
-----------------------------------------
>From ZIP application note:
{quote}
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.
{quote}
> Unix timestamps since the epoch are not subject to the boundary checks
> ----------------------------------------------------------------------
>
> Key: MSHARED-1445
> URL: https://issues.apache.org/jira/browse/MSHARED-1445
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-3.6.2
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Critical
> Fix For: maven-archiver-4.0.0, maven-archiver-3.6.3,
> maven-archiver-4.0.0-beta-2
>
>
> The Javadoc says:
> {noformat}
> * @throws IllegalArgumentException if the outputTimestamp is neither ISO 8601
> nor an integer, or it's not within
> * the valid range 1980-01-01T00:00:02Z to 2099-12-31T23:59:59Z
> {noformat}
> but when a Unix timestamp since the epoch is passed it is simply passed
> through. No min/max check. We need to fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
