You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/03/27 13:43:00 UTC

[jira] [Updated] (MGPG-116) Up the file size limit to 64K

     [ https://issues.apache.org/jira/browse/MGPG-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamas Cservenak updated MGPG-116:
---------------------------------
    Description: 
The refd document talks about "key size" (that is very rarely 16K), but the file we are loading up is armored: Base64 encoded + formatted  + newlines and may have arbitrary amount of comments added as well.

In short, the wiki talks about the "key size" as in memory, while this file have much of the overhead, plus, it may be collection of keys...

  was:
The refd document talks about "key size" (that is very rarely 16K), but the file we are loading up is armored (Base64 encoded + formatted  + newlines and may have arbitrary amount of comments added as well).

In short, the wiki talks about the "key size" as in memory, while this file have much of the overhead, plus, it may be collection of keys...


> Up the file size limit to 64K
> -----------------------------
>
>                 Key: MGPG-116
>                 URL: https://issues.apache.org/jira/browse/MGPG-116
>             Project: Maven GPG Plugin
>          Issue Type: Task
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 3.2.3
>
>
> The refd document talks about "key size" (that is very rarely 16K), but the file we are loading up is armored: Base64 encoded + formatted  + newlines and may have arbitrary amount of comments added as well.
> In short, the wiki talks about the "key size" as in memory, while this file have much of the overhead, plus, it may be collection of keys...



--
This message was sent by Atlassian Jira
(v8.20.10#820010)