| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 43 |
2831d 08h |
magnus |
/trunk/debian/ |
Drop libtar/Makefile from examples, since it makes the build
unreproducible (saves $SHELL) and isn't enough to compile libtar.c
anyway. |
|
| 42 |
2960d 10h |
magnus |
/tags/1.2.20-5/ |
[svn-buildpackage] Tagging libtar 1.2.20-5 |
|
| 41 |
2960d 11h |
magnus |
/trunk/debian/ |
Bump Standards-Version to 3.9.7. |
|
| 40 |
2960d 11h |
magnus |
/trunk/debian/ |
Don't bother checking for zlib, which is only used by the example binary (libtar). |
|
| 39 |
2960d 11h |
magnus |
/trunk/debian/ |
testsuite.patch: Add a simple test (Closes: #737258). |
|
| 38 |
3490d 09h |
magnus |
/trunk/debian/ |
oldgnu_prefix.patch: Detect old-style GNU headers correctly (Closes:
#763119). Those appear in incremental archives and use the bytes that
the new-style headers use for the prefix field for other fields.
Thanks to Steinar H. Gunderson. |
|
| 37 |
3652d 10h |
magnus |
/tags/1.2.20-4/ |
[svn-buildpackage] Tagging libtar 1.2.20-4 |
|
| 36 |
3652d 10h |
magnus |
/trunk/debian/ |
no_maxpathlen.patch: Half of the part of the patch modifying
compat/dirname.c was missing, causing libtar's dirname to always
return NULL (except in special circumstances). Actually make it work
(Closes: #745352). (The reason that libtar doesn't use libc's
dirname() and basename() on some or most platforms is that the code
doesn't work with destructive versions of these functions). |
|
| 35 |
3728d 11h |
magnus |
/branches/wheezy/debian/ |
[SECURITY] CVE-2013-4420.patch: Strip out leading slashes and any
pathname prefix containing ".." components (Closes: #731860). This is
done in th_get_pathname() (as well as to symlink targets when
extracting symlinks), not merely when extracting files, which means
applications calling that function will not see the stored
filename. There is no way to disable this behaviour, but it can be
expected that one will be provided when the issue is solved upstream. |
|
| 34 |
3729d 06h |
magnus |
/tags/1.2.20-3/ |
[svn-buildpackage] Tagging libtar 1.2.20-3 |
|
| 33 |
3729d 06h |
magnus |
/trunk/debian/ |
th_get_size-unsigned-int.patch: Make the th_get_size() macro cast the
result from oct_to_int() to unsigned int. This is the right fix for
bug #725938 on 64-bit systems, where a specially crafted tar file
would not cause an integer overflow, but a memory allocation of almost
16 exbibytes, which would certainly fail outright without harm. |
|
| 32 |
3729d 06h |
magnus |
/trunk/debian/patches/ |
Add stdlib.h for malloc() in lib/decode.c |
|
| 31 |
3729d 07h |
magnus |
/trunk/debian/ |
[SECURITY] CVE-2013-4420.patch: When the prefix field is in use, the
safer_name_suffix() function should certainly be applied to the
combination of it and the name field, not just on the name field. |
|
| 30 |
3729d 07h |
magnus |
/trunk/debian/ |
no_maxpathlen.patch: Fix two grave bugs in the patch. First,
th_get_pathname would only allocate as much memory as was needed for
the first filename encountered, causing heap corruption when/if
encountering longer filenames later. Second, two variables were mixed
up in tar_append_tree(). Also, fix a potential memory leak and trim
the patch a bit. |
|
| 29 |
3729d 07h |
magnus |
/trunk/debian/ |
Correct patch name in changelog. |
|
| 28 |
3729d 08h |
magnus |
/tags/1.2.16-1+deb7u1/ |
[svn-buildpackage] Tagging libtar 1.2.16-1+deb7u1 |
|
| 27 |
3729d 08h |
magnus |
/branches/wheezy/debian/ |
[SECURITY] size_t-overflow_cve-2013-4397.patch: Fix CVE-2013-4397:
Integer overflow (Closes: #725938). |
|
| 26 |
3729d 08h |
magnus |
/tags/1.2.20-2/ |
[svn-buildpackage] Tagging libtar 1.2.20-2 |
|
| 25 |
3729d 08h |
magnus |
/trunk/debian/ |
Bump Standards-Version to 3.9.5. |
|
| 24 |
3729d 08h |
magnus |
/trunk/debian/ |
[SECURITY] CVE-2013-4420.patch: Strip out leading slashes and any
pathname prefix containing ".." components (Closes: #731860). This is
done in th_get_pathname() (as well as to symlink targets when
extracting symlinks), not merely when extracting files, which means
applications calling that function will not see the stored
filename. There is no way to disable this behaviour, but it can be
expected that one will be provided when the issue is solved upstream. |
|