Zlib header not detected by offzip
up vote
1
down vote
favorite
I'm looking into a file that contains some zlib compressed chunks, some are detected by Offzip as valid, one is not:
0x 78 01 F3 48 --valid and has a matching adler32 hash
0x 78 01 03 00 --invalid
0x 78 01 63 64 --valid not sure about the hash
I think it's only the first three bytes that indicate the compression method and flags, so I'm unsure as to why the second entry is not detected. It certainly looks like a zlib data block, but I'm a bit lost
Any input or advice would be greatly appreciated
c# compression zlib dotnetzip
add a comment |
up vote
1
down vote
favorite
I'm looking into a file that contains some zlib compressed chunks, some are detected by Offzip as valid, one is not:
0x 78 01 F3 48 --valid and has a matching adler32 hash
0x 78 01 03 00 --invalid
0x 78 01 63 64 --valid not sure about the hash
I think it's only the first three bytes that indicate the compression method and flags, so I'm unsure as to why the second entry is not detected. It certainly looks like a zlib data block, but I'm a bit lost
Any input or advice would be greatly appreciated
c# compression zlib dotnetzip
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm looking into a file that contains some zlib compressed chunks, some are detected by Offzip as valid, one is not:
0x 78 01 F3 48 --valid and has a matching adler32 hash
0x 78 01 03 00 --invalid
0x 78 01 63 64 --valid not sure about the hash
I think it's only the first three bytes that indicate the compression method and flags, so I'm unsure as to why the second entry is not detected. It certainly looks like a zlib data block, but I'm a bit lost
Any input or advice would be greatly appreciated
c# compression zlib dotnetzip
I'm looking into a file that contains some zlib compressed chunks, some are detected by Offzip as valid, one is not:
0x 78 01 F3 48 --valid and has a matching adler32 hash
0x 78 01 03 00 --invalid
0x 78 01 63 64 --valid not sure about the hash
I think it's only the first three bytes that indicate the compression method and flags, so I'm unsure as to why the second entry is not detected. It certainly looks like a zlib data block, but I'm a bit lost
Any input or advice would be greatly appreciated
c# compression zlib dotnetzip
c# compression zlib dotnetzip
edited Nov 19 at 19:32
asked Nov 19 at 18:20
Tony
1,44552849
1,44552849
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
Those are all valid starts to zlib streams. Of course, none of them are valid entire zlib streams, since the minimum zlib stream length is eight bytes.
The 78 01 03 00 has a valid zlib header, 78 01, and a valid and in fact complete deflate stream, 03 00. That is an empty fixed codes deflate block marked as the last block. If you follow that with 00 00 00 01 (the Adler-32 check value for zero bytes), then you have a complete and correct zlib stream.
Thanks for the info Mark. I am indeed seeing an empty and complete zlib stream. Is there a common use for empty streams like this? For use as a marker of some kind?
– Tony
Nov 20 at 7:54
1
I have no idea how common empty zlib streams are. However the tool clearly has a bug if it is marking that as not the start of a valid zlib stream.
– Mark Adler
Nov 20 at 15:33
Thanks Mark. Appreciate the information.
– Tony
Nov 21 at 13:30
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Those are all valid starts to zlib streams. Of course, none of them are valid entire zlib streams, since the minimum zlib stream length is eight bytes.
The 78 01 03 00 has a valid zlib header, 78 01, and a valid and in fact complete deflate stream, 03 00. That is an empty fixed codes deflate block marked as the last block. If you follow that with 00 00 00 01 (the Adler-32 check value for zero bytes), then you have a complete and correct zlib stream.
Thanks for the info Mark. I am indeed seeing an empty and complete zlib stream. Is there a common use for empty streams like this? For use as a marker of some kind?
– Tony
Nov 20 at 7:54
1
I have no idea how common empty zlib streams are. However the tool clearly has a bug if it is marking that as not the start of a valid zlib stream.
– Mark Adler
Nov 20 at 15:33
Thanks Mark. Appreciate the information.
– Tony
Nov 21 at 13:30
add a comment |
up vote
2
down vote
accepted
Those are all valid starts to zlib streams. Of course, none of them are valid entire zlib streams, since the minimum zlib stream length is eight bytes.
The 78 01 03 00 has a valid zlib header, 78 01, and a valid and in fact complete deflate stream, 03 00. That is an empty fixed codes deflate block marked as the last block. If you follow that with 00 00 00 01 (the Adler-32 check value for zero bytes), then you have a complete and correct zlib stream.
Thanks for the info Mark. I am indeed seeing an empty and complete zlib stream. Is there a common use for empty streams like this? For use as a marker of some kind?
– Tony
Nov 20 at 7:54
1
I have no idea how common empty zlib streams are. However the tool clearly has a bug if it is marking that as not the start of a valid zlib stream.
– Mark Adler
Nov 20 at 15:33
Thanks Mark. Appreciate the information.
– Tony
Nov 21 at 13:30
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Those are all valid starts to zlib streams. Of course, none of them are valid entire zlib streams, since the minimum zlib stream length is eight bytes.
The 78 01 03 00 has a valid zlib header, 78 01, and a valid and in fact complete deflate stream, 03 00. That is an empty fixed codes deflate block marked as the last block. If you follow that with 00 00 00 01 (the Adler-32 check value for zero bytes), then you have a complete and correct zlib stream.
Those are all valid starts to zlib streams. Of course, none of them are valid entire zlib streams, since the minimum zlib stream length is eight bytes.
The 78 01 03 00 has a valid zlib header, 78 01, and a valid and in fact complete deflate stream, 03 00. That is an empty fixed codes deflate block marked as the last block. If you follow that with 00 00 00 01 (the Adler-32 check value for zero bytes), then you have a complete and correct zlib stream.
answered Nov 20 at 2:15
Mark Adler
56.9k760107
56.9k760107
Thanks for the info Mark. I am indeed seeing an empty and complete zlib stream. Is there a common use for empty streams like this? For use as a marker of some kind?
– Tony
Nov 20 at 7:54
1
I have no idea how common empty zlib streams are. However the tool clearly has a bug if it is marking that as not the start of a valid zlib stream.
– Mark Adler
Nov 20 at 15:33
Thanks Mark. Appreciate the information.
– Tony
Nov 21 at 13:30
add a comment |
Thanks for the info Mark. I am indeed seeing an empty and complete zlib stream. Is there a common use for empty streams like this? For use as a marker of some kind?
– Tony
Nov 20 at 7:54
1
I have no idea how common empty zlib streams are. However the tool clearly has a bug if it is marking that as not the start of a valid zlib stream.
– Mark Adler
Nov 20 at 15:33
Thanks Mark. Appreciate the information.
– Tony
Nov 21 at 13:30
Thanks for the info Mark. I am indeed seeing an empty and complete zlib stream. Is there a common use for empty streams like this? For use as a marker of some kind?
– Tony
Nov 20 at 7:54
Thanks for the info Mark. I am indeed seeing an empty and complete zlib stream. Is there a common use for empty streams like this? For use as a marker of some kind?
– Tony
Nov 20 at 7:54
1
1
I have no idea how common empty zlib streams are. However the tool clearly has a bug if it is marking that as not the start of a valid zlib stream.
– Mark Adler
Nov 20 at 15:33
I have no idea how common empty zlib streams are. However the tool clearly has a bug if it is marking that as not the start of a valid zlib stream.
– Mark Adler
Nov 20 at 15:33
Thanks Mark. Appreciate the information.
– Tony
Nov 21 at 13:30
Thanks Mark. Appreciate the information.
– Tony
Nov 21 at 13:30
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53380536%2fzlib-header-not-detected-by-offzip%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown