!c99Shell v. 1.0 pre-release build #16!

Software: Apache/2.2.3 (CentOS). PHP/5.1.6 

uname -a: Linux mx-ll-110-164-51-230.static.3bb.co.th 2.6.18-194.el5PAE #1 SMP Fri Apr 2 15:37:44
EDT 2010 i686 

uid=48(apache) gid=48(apache) groups=48(apache) 

Safe-mode: OFF (not secure)

/usr/share/doc/netpbm-10.35.58/userguide/   drwxr-xr-x
Free 50.93 GB of 127.8 GB (39.85%)
Home    Back    Forward    UPDIR    Refresh    Search    Buffer    Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    


Viewing file:     pamfixtrunc.html (3.12 KB)      -rw-r--r--
Select action/file-type:
(+) | (+) | (+) | Code (+) | Session (+) | (+) | SDB (+) | (+) | (+) | (+) | (+) | (+) |
Pamfixtrunc User Manual

pamfixtrunc

Updated: 06 January 2006
Table Of Contents

NAME

pamfixtrunc - repair a Netpbm image whose file is truncated

SYNOPSIS

pamfixtrunc [-verbose] [netpbmfile]

DESCRIPTION

This program is part of Netpbm.

pamfixtrunc reads as much as it can of a Netpbm image that may be truncated (i.e. the file may not contain the last part of the image) and writes out a valid Netpbm image that is just missing the bottom rows of the original (pre-truncation) image.

The header of a Netpbm image implies how large the image must be (how many bytes the file must contain). If the file is actually smaller than that, a Netpbm program that tries to read the image fails, with an error message telling you that it couldn't read the whole file. The data in the file is arranged in row order, from top to bottom, and the most common reason for the file being smaller than its header says it should be is because the bottommost rows are simply missing. So pamfixtrunc assumes that is the case and generates a new image with just the rows that are readable. (technically, that means the output's header indicates a smaller number of rows and omits any partial last row).

The most common way for a Netpbm file to be small is that something interrupted the program that generated it before it was finished writing the file. For example, the program ran out of its own input or encountered a bug or ran out of space in which to write the output.

Another problem pamfixtrunc deals with is where the file isn't actually too small, but due to a system error, a byte in the middle of it cannot be read (think of a disk storage failure). pamfixtrunc reads the input sequentially until it can't read any further, for any reason. So it treats such an image as a truncated one, ignoring all data after the unreadable byte.

But be aware that an image file is sometimes too small because of a bug in the program that generated it, and in that case it is not simply a matter of the bottom of the image missing, so pamfixtrunc simply creates a valid Netpbm image containing a garbage picture.

pamfixtrunc looks at only on the first image in a multi-image stream.

If you want to test an image file to see if it is corrupted by being too small, use pamfile --allimages . It fails with an error message if the file is too small.

If you want to cut the bottom off a valid Netpbm image, use pamcut.

SEE ALSO

pnm, pam, pamcut, pamfile,

HISTORY

pamfixtrunc was new in Netpbm 10.38 (March 2007).

Table Of Contents


:: Command execute ::

Enter:
 
Select:
 

:: Shadow's tricks :D ::

Useful Commands
 
Warning. Kernel may be alerted using higher levels
Kernel Info:

:: Preddy's tricks :D ::

Php Safe-Mode Bypass (Read Files)

File:

eg: /etc/passwd
Php Safe-Mode Bypass (List Directories):

Dir:

eg: /etc/

:: Search ::
  - regexp 
:: Upload ::
 
[ Read-Only ]

:: Make Dir ::
 
[ Read-Only ]
:: Make File ::
 
[ Read-Only ]

:: Go Dir ::
 
:: Go File ::
 

--[ c999shell v. 1.0 pre-release build #16 Modded by Shadow & Preddy | RootShell Security Group | r57 c99 shell | Generation time: 0.0059 ]--