I'm not actually finished with this, but I do have a local backup anyway,
closing is okay.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835#issuecomment-1905561075
You are receiving this because you are subscribed to this thread.
Closed #2835.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835#event-11563746414
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
Understood, thanks! Feel free to close this once you're done with it.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835#issuecomment-1901738765
You are receiving this because you are subscribed to this thread.
Message ID:
The more I looked at this and the existing docs, the more clear it became that
the stuff needs more than a touch-up job to be credible.
I ended up rewriting much of bit of it, updating and preserving the v3 docs too
for historians and the like: #2861. That was quite the pile to chew out in a
Updated
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835#issuecomment-1884986428
You are receiving this because you are subscribed to this thread.
Message ID: ___
Rpm-maint mailing list
@dralley pushed 1 commit.
eb08565561b42ded13fea02054312a75553eebae Clean up immutable regions section a
bit
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835/files/9f3185cb7bf13f78ad557116325fe75c452944e6..eb08565561b42ded13fea02054312a75553eebae
You are receiving
@pmatilai commented on this pull request.
> @@ -24,16 +24,19 @@ package file is divided in 4 logical sections:
```
All 2 and 4 byte "integer" quantities (int16 and int32) are stored in
Sorry, forgot to mention this yesterday: we also have 64bit integers where this
also applies.
--
Reply
@pmatilai commented on this pull request.
> @@ -264,3 +256,101 @@ could start at byte 589, byte that is an improper
> boundary for an INT32.
As a result, 3 null bytes are inserted and the date for the SIZE actually
starts at byte 592: "00 09 9b 31", which is 629553).
+### Immutable header
@dralley pushed 3 commits.
f161a47fa0ff1349acfd5fa62a58fc2b88a3650d Update format documentation in the
manual
e452eab72b4df2c9ae8ad8bbcc8a9a2acf1c2b0f Merge header regions document into
format document
9f3185cb7bf13f78ad557116325fe75c452944e6 Clean up immutable regions section a
bit
--
@dralley commented on this pull request.
> @@ -264,3 +256,101 @@ could start at byte 589, byte that is an improper
> boundary for an INT32.
As a result, 3 null bytes are inserted and the date for the SIZE actually
starts at byte 592: "00 09 9b 31", which is 629553).
+### Immutable header
@dralley commented on this pull request.
> # Package format
-This document describes the RPM file format version 3.0, which is used
-by RPM versions 2.1 and greater. The format is subject to change, and
-you should not assume that this document is kept up to date with the
-latest RPM code.
@dralley pushed 1 commit.
cbebd9eccf2d57132c676a5b14996e8616e4d42b Clean up immutable regions section a
bit
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835/files/64b4c81b4ae9d1599084676d1a8f999bfc11abfc..cbebd9eccf2d57132c676a5b14996e8616e4d42b
You are receiving
@dralley pushed 3 commits.
1ece805fc54d31715afdc56c7dbb0d35a82863bd Update format documentation in the
manual
73403c2ad734c2b816c0f881ac2e822b13bbf7ab Merge header regions document into
format document
64b4c81b4ae9d1599084676d1a8f999bfc11abfc Clean up immutable regions section a
bit
--
@dralley commented on this pull request.
> # Package format
-This document describes the RPM file format version 3.0, which is used
-by RPM versions 2.1 and greater. The format is subject to change, and
-you should not assume that this document is kept up to date with the
-latest RPM code.
@pmatilai commented on this pull request.
> +they store can be found [here](signatures_digests.md).
+
+RPM v4 packages are expected to contain at least one of SHA1HEADER or
SHA256HEADER
+tags, providing a cryptographic digest of the main header, and may contain one
+or both of the
@pmatilai commented on this pull request.
> @@ -435,7 +435,7 @@ typedef enum rpmSigTag_e {
RPMSIGTAG_RESERVEDSPACE = 1008,/*!< internal space reserved for signatures
*/
RPMSIGTAG_BADSHA1_1= RPMTAG_BADSHA1_1, /*!< internal Broken
SHA1, take 1. */
RPMSIGTAG_BADSHA1_2
@pmatilai commented on this pull request.
>
Tag Name | Value| Type | Description
--|--|--|
-Dsaheader | 267 | bin | OpenPGP DSA signature of the header
(if thus signed)
-Longsigsize | 270 | int64|
@pmatilai commented on this pull request.
> +unique tags (just like the Header). Details about these tags and the
> information
+they store can be found [here](signatures_digests.md).
+
+RPM v4 packages are expected to contain at least one of SHA1HEADER or
SHA256HEADER
+tags, providing a
@pmatilai commented on this pull request.
> -header structure:
-
-```
- NameTag Header Type
- ---
- SIZE1000INT_32
- MD5 1001BIN
- PGP 1002BIN
-```
-
-The MD5 signature is 16 bytes, and the PGP signature
@pmatilai commented on this pull request.
>
```
0008: 00 01 72 70 6d 2d 32 2e..rpm-2.
```
-The next two bytes (8-9) form an int16 that indicates the architecture
-the package was built for. While this is used by file(1), the true
-architecture is stored as a string in the
@pmatilai commented on this pull request.
> @@ -23,17 +23,20 @@ package file is divided in 4 logical sections:
. Payload -- compressed archive of the file(s) in the package (aka "payload")
```
-All 2 and 4 byte "integer" quantities (int16 and int32) are stored in
-network byte order.
@pmatilai commented on this pull request.
> # Package format
-This document describes the RPM file format version 3.0, which is used
-by RPM versions 2.1 and greater. The format is subject to change, and
-you should not assume that this document is kept up to date with the
-latest RPM code.
@dralley commented on this pull request.
> @@ -229,7 +216,7 @@ In our example there would be 32 such 16-byte index
> entries, followed
by the data section:
```
-0210: 72 70 6d 00 32 2e 31 2e 32 00 31 00 52 65 64 20rpm.2.1.2.1.Red
+0210: 72 70 6d 00 32 2e 31 2e 32 00 31 00 52
@dralley pushed 1 commit.
c579fbf1a914f96fa14465acec97390197740f54 Update format documentation in the
manual
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835/files/dbd7eb8f93c9804ff37ae22ef8d01f507b384318..c579fbf1a914f96fa14465acec97390197740f54
You are
@jobol commented on this pull request.
> @@ -229,7 +216,7 @@ In our example there would be 32 such 16-byte index
> entries, followed
by the data section:
```
-0210: 72 70 6d 00 32 2e 31 2e 32 00 31 00 52 65 64 20rpm.2.1.2.1.Red
+0210: 72 70 6d 00 32 2e 31 2e 32 00 31 00 52 65
@dralley pushed 1 commit.
dbd7eb8f93c9804ff37ae22ef8d01f507b384318 Update format documentation in the
manual
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835/files/f44637672c6096f2dac5e5b87291b9fbb06da6f7..dbd7eb8f93c9804ff37ae22ef8d01f507b384318
You are
@dralley pushed 1 commit.
f44637672c6096f2dac5e5b87291b9fbb06da6f7 Update format documentation in the
manual
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835/files/b891bfcbacb824507cd3527cfa5951c24be55bd4..f44637672c6096f2dac5e5b87291b9fbb06da6f7
You are
@dralley commented on this pull request.
>
```
0008: 00 01 72 70 6d 2d 32 2e..rpm-2.
```
-The next two bytes (8-9) form an int16 that indicates the architecture
-the package was built for. While this is used by file(1), the true
-architecture is stored as a string in the Header.
@dralley pushed 1 commit.
b891bfcbacb824507cd3527cfa5951c24be55bd4 Update format documentation in the
manual
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835/files/a561596b015506565c2370559586156b5db0293b..b891bfcbacb824507cd3527cfa5951c24be55bd4
You are
@dralley commented on this pull request.
> +
+The Signature can contain multiple different types of signatures, stored under
+unique tags (just like the Header). Details about these tags and the
information
+they store can be found [here](signatures_digests.md).
+
+RPM v4 packages are expected
@dralley pushed 1 commit.
6ede171288e5bb6e565818e988cfa4bf69962367 Update format documentation in the
manual
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2835/files/5bfcfa058cdd7c6a93c2d96e02dea9fc044b5476..6ede171288e5bb6e565818e988cfa4bf69962367
You are
@dralley commented on this pull request.
>
## Signature
-A 3.0 format signature (denoted by signature type 5 in the Lead), uses
-the same structure as the Header. For historical reasons, this
-structure is called a "header structure", which can be confusing since
-it is used for both the
@dralley commented on this pull request.
>
```
: ed ab ee db 03 00 00 00
```
-The first 4 bytes (0-3) are "magic" used to uniquely identify an RPM
-package. It is used by RPM and file(1). The next two bytes (4, 5)
-are int8 quantities denoting the "major" and "minor" RPM file
@dralley commented on this pull request.
> @@ -23,17 +23,20 @@ package file is divided in 4 logical sections:
. Payload -- compressed archive of the file(s) in the package (aka "payload")
```
-All 2 and 4 byte "integer" quantities (int16 and int32) are stored in
-network byte order. When
Make it (mostly) up to date with RPMv4 standards.
Also fix some broken links, and mark old signature tags as deprecated.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/2835
-- Commit Summary --
* Update format
35 matches
Mail list logo
