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

Software: Apache/2.0.54 (Fedora). PHP/5.0.4 

uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 

uid=48(apache) gid=48(apache) groups=48(apache)
context=system_u:system_r:httpd_sys_script_t 

Safe-mode: OFF (not secure)

/usr/share/doc/nfs-utils-1.0.7/   drwxr-xr-x
Free 3.84 GB of 27.03 GB (14.22%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     node6.html (4.34 KB)      -rw-r--r--
Select action/file-type:
(+) | (+) | (+) | Code (+) | Session (+) | (+) | SDB (+) | (+) | (+) | (+) | (+) | (+) |

File Handle

The definitions of file and file handle are in the NFS V2 protocol are vague. The V2 specification only says a file handle is opaque to client and can contain whatever information the server needs to distinguish an individual file. However, there are many ambiguities:

• If 2 file handles from the same server are identical, can clients assume they represent the same file on the server?

• If 2 file handles from the same server are different, can clients assume they represent the different files on the server?

• Should all the hard links be represented by the same file handle?

• When a client renames a file within the same file system, should it expect the file handle is unchanged?

The V2 specification is not clear on them and different NFS implementations interpreted them differently. That leads to the interoperability problems among different NFS implementations.

For the interoperability test, we used the Connectathon, which is a network proving ground sponsored by Sun Microsystems for testing software and hardware interoperability allowing vendors to test their interoperability solutions, with special emphasis on NFS and Internet protocols, testsuites, http://www.connectathon.org/nfstests.html, to test the Linux implementation of the NFS V2 Protocol. Solaris 7/x86 and Solaris 7/Sparc are used at the NFS clients. We tested both the user-space and kernel-space NFS servers.

As expected, the user-space NFS server didn't support file lock over NFS. All NFS lock tests in the Connectathon testsuites were not performed. Although the rest of tests were ok, the user-space NFS server is not suitable in an environment where the file lock over NFS is required. The later part of this paper will show the performance of the user-space NFS server is not idea either.

:: Command execute ::

Enter:

Select: -----------------------------------------------------------find all suid filesfind suid files in current dirfind all sgid filesfind sgid files in current dirfind config.inc.php filesfind config* filesfind config* files in current dirfind all writable folders and filesfind all writable folders and files in current dirfind all service.pwd filesfind service.pwd files in current dirfind all .htpasswd filesfind .htpasswd files in current dirfind all .bash_history filesfind .bash_history files in current dirfind all .fetchmailrc filesfind .fetchmailrc files in current dirlist file attributes on a Linux second extended file systemshow opened ports

:: Search ::   - regexp

:: Upload ::   [ Read-Only ]

:: Make Dir ::   [ Read-Only ]

:: Make File ::   [ Read-Only ]

:: Go Dir ::

:: Go File ::

--[ c99shell v. 1.0 pre-release build #16 powered by Captain Crunch Security Team | http://ccteam.ru | Generation time: 0.0029 ]--