Call: +44 (0)1904 557620 Call
Forum

Welcome, Guest. Please Login.
Apr 25th, 2024, 5:53pm
News: If you would like to register contact the forum admin
Home | Help | Search | Members | Login
   Pete Finnigan's Oracle Security Forum
   Oracle Security
   Oracle Security
(Moderator: Pete Finnigan)
   Key and algo for encrypting the listener password.
« Previous topic | Next topic »
Pages: 1  Reply | Notify of replies | Send Topic | Print
   Author  Topic: Key and algo for encrypting the listener password.  (Read 12910 times)
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Key and algo for encrypting the listener password.
« on: Jul 28th, 2007, 2:14am »
Quote | Modify

Hi,
 
I would like to know the key and algorithm used for encrypting the listener password. I see that if I set the password on the server using change_password, and use the same password (in clear text) on the lsnrctl prompt (run on remote machine) using set password, the password is encrypted/hashed while being sent to server (seen using tcpdump).
 
I want to use it in my C code (from remote machine)to communicate with the listener (on the server), hence I am interested in knowing the key/algo for the same.
 
The listener.ora, sqlnet.ora and tnsnames.ora file does not contain any key/algo specifications, hence the values must be default.
 
Kindly excuse if I am not clear as I am new to this domain.
 
Any help is highly appreciated.
 
Regards,
Riz.
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Key and algo for encrypting the listener passw
« Reply #1 on: Jul 28th, 2007, 8:08am »
Quote | Modify

Riz,
 
The Oracle TNS Listener is using the Oracle password algorithm (from the database) to hash the listener password using the change_password command.
 
People often misunderstand this concept.
 
There are 2 ways to set the listener password with the set password command:
1. set password tiger
2. set password <CR>
   password: tiger
 
In the first case the string "tiger" is sent in cleartext, in the second case the string "tiger" is hashed with the Oracle password algorithm and the result (=hash value) is sent in cleartext.
 
For an attacker there is no difference if he intercepts the string because this string is used for the listeneer authentication. The attacker just uses the
 
  set password E7C4...
 
to send the hash value.
The hashing algorithm is only used to generate a (random) string. The hashing algorithm is only useful for dictionary attacks against the TNS listener (e.g. for hashing a dictionary file).
 
Hope this helps.
 
 Alexander
 
--
Alexander Kornbrust
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Key and algo for encrypting the listener passw
« Reply #2 on: Aug 2nd, 2007, 12:45am »
Quote | Modify

Hi Alexander,
 
Thanks for taking time out but as observed the password sent over the network is always the encrypted as shown below
 
"DESCRIPTION=(CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=oracle))(COMMAND= status)(ARGUMENTS=64)(PASSWORD=125916DFCEFE8F08)(SERVICE=)(VERSION=)))"
 
irrespective of the way the password was entered  
 
1) set password <passwd> or  
2) set paswprd <CR>  
    password: <passwd>.
 
Also, the Oracle password algorithm as mentions on red-database-security that the username is concatenated to the user's password, and "all characters will be converted to uppercase before the hashing starts 8-byte hash, encrypted with a DES encryption algorithm without real salt (just the username)".
 
but as I have observed, irrespective of the username used, the encrypted password is always same for a password "welcome" (125916DFCEFE8F08), which indicates that username is not used in calculating the password for listener authentication.
 
Hence, my original query still stands about the algo used for encrypting the listner password.
 
Thanks in advance,
Riz
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Key and algo for encrypting the listener passw
« Reply #3 on: Aug 2nd, 2007, 10:25pm »
Quote | Modify

Riz,
 
what version of Oracle do you use? That's important. Oracle changed the behaviour of the set password command in some newer versions (AFAIK with 9206/9207).
 
The listener does not have an username that's why Oracle is using the artificial username "arbitrary" instead, e.g.
hash(ARBITRARYWELCOME).
 
---
#----ADDED BY TNSLSNR 22-MAR-2006 01:21:55---
PASSWORDS_LISTENER = C75FBC1C9FA2F2D3
#--------------------------------------------
 
D:\orabf>oraclehash arbitrary v1enna
c75fbc1c9fa2f2d3:arbitrary
--
 
In some versions of 64 bit operating systems there was a problem in the implementation of this algorithm. But in most OS the Oracle password algorithm should work.  
 
I hope this solves the problem.
 
Regards
 
 Alexander
--
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pete Finnigan
PeteFinnigan.com Administrator
*****




Oracle Security is easier if you design for it

   
View Profile | WWW | Email

Gender: male
Posts: 309
Re: Key and algo for encrypting the listener passw
« Reply #4 on: Jan 22nd, 2010, 11:30pm »
Quote | Modify

There is a detailed description for this algo:
 marcellmajor.com/frame_listenerhash.html - (broken link)
IP Logged

Pete Finnigan (email:pete@petefinnigan.com)
Oracle Security Web site: http://www.petefinnigan.com
Forum: http://www.petefinnigan.com/forum/yabb/YaBB.cgi
Oracle security blog: http://www.petefinnigan.com/weblog/entries/index.html
Pages: 1  Reply | Notify of replies | Send Topic | Print

« Previous topic | Next topic »

Powered by YaBB 1 Gold - SP 1.4!
Forum software copyright © 2000-2004 Yet another Bulletin Board
  • PFCLScan PFCLScan

    Simply connect PFCLScan to your Oracle database and it will automatically discover the security issues that could make your Oracle database vulnerable to attack and to the potential loss of your data.

  • PFCL Obfuscate PFCLObfuscate

    PFCLObfuscate is the only tool available that can automatically add license controls to your PL/SQL code. PFCLObfuscate protects your Intellectual Property invested in your PL/SQL database code.

  • PFCLCode PFCLCode

    PFCLCode is a tool to allow you to analyse your PL/SQL code for many different types of security issues. PFCLCode gives you a detailed review and reports and includes a powerful colour syntax highlighting code editor

  • PFCLForensics PFCLForensics

    PFCLForensics is the only tool available to allow you to do a detailed live response of a breached Oracle database and to then go on and do a detailed forensic analysis of the data gathered.

  • Products We resell PFCLReselling

    PeteFinnigan.com Limited has partnered with a small number of relevant companies to resell their products where they enhance or compliment what we do

  • PFCLATK PFCLATK

    PFCLATK is a toolkit that allows detailed pre-defined policy driven audit trails for your Oracle database. The toolkit also provides for a centralised audit trail and centralised activity reporting

  • PFCLCookie PFCLCookie

    PFCLCookie is a useful tool to use to audit your websites for tracking cookies. Scan websites in a natural way using powerful browser driven scanner

  • PFCL Training PFCLTraining

    PFCLTraining is a set of expert training classes for you, aimed at teaching how to audit your own Oracle database, design audit trails, secure code in PL/SQL and secure and lock down your Oracle database.

  • PFCL Services PFCLServices

    Choose PFCLServices to add PeteFinnigan.com Ltd to your team for your Oracle Security needs. We are experts in performing detailed security audits, data security design work and policy creation

  • PFCLConsulting PFCLConsulting

    Choose PFCLConsulting to ask PeteFinnigan.com Limited to set up and use our products on your behalf

  • PFCLCustom PFCLCustom

    All of our software products can be customised at a number of levels. Choose this to see how our products can be part of your products and services

  • PFCLCloud PFCLCloud

    Private cloud, public cloud, hybrid cloud or no cloud. Learn how all of our services, trainings and products will work in the cloud

  • PFCLUserRights PFCLUserRights

    PFCLUserRights allows you to create a very detailed view of database users rights. The focus of the reports is to allow you to decide what privileges and accounts to keep and which to remove.

  • PFCLSTK PFCLSTK

    PFCLSTK is a toolkit application that allows you to provide database security easily to an existing database. PFCLSTK is a policy driven toolkit of PL/SQL that creates your security

  • PFCLSFTK PFCLSFTK

    PFCLSFTK is a toolkit that solves the problem of securing third party applications written in PL/SQL. It does this by creating a thin layer between the application and database and this traps SQL Injection attempts. This is a static firewall.

  • PFCLSEO PFCLSEO

    PFCLSEO is a web scanner based on the PFCLScan technology so that a user can easily scan a website for technical SEO issues