| Anonymous | Login | Signup for a new account | 11-10-2008 10:53 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000547 | [BusyBox] Standards Compliance | major | always | 11-16-05 09:07 | 01-08-06 19:09 | ||||
| Reporter | aforet | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 1.00 | ||||||
| Summary | 0000547: tar archive corruption when packing unreadable files | ||||||||
| Description |
When trying to pack a file not readable in a tarball, the Busybox tar applet includes an header describing the file to the tar archive, but with no content. The resulting archive is corrupted. For instance: $ id uid=500(johndoe) gid=100(users) groups=100(users) $ ls -l file? -rw-r--r-- 1 johndoe users 20 nov 2 2005 file1 -rw------- 1 root root 20 nov 2 2005 file2 -rw-r--r-- 1 johndoe users 20 nov 2 2005 file3 $ cat file1 this is file 1 $ cat file2 this is file 2 $ cat file3 this is file 3 $ ./busybox tar cvf test.tar file1 file2 file3 file3 file2 tar: file2: Cannot open: Permission non accord |
||||||||
| Additional Information |
BTW, tar reports errors when trying to create the archive, however the returned error code is 0! Same thing when trying to list the content of the corrupted archived: BB tar failed to fully display it, but it still returns 0 as the error code... |
||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |