db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-928) Add ability to network server to accept connections with a certain security mechanism.
Date Tue, 28 Feb 2006 17:30:43 GMT
     [ http://issues.apache.org/jira/browse/DERBY-928?page=all ]

Sunitha Kambhampati updated DERBY-928:
--------------------------------------

    Attachment: Derby928.3.stat.txt
                Derby928.3.diff.txt

http://www.nabble.com/-jira-Created%3A-%28DERBY-928%29-Add-ability-to-network-server-to-accept-connections-with-a-certain-security-mechanism.-t1073183.html

Thanks very much Deepa for reviewing this issue. 

Some changes went into testSecMec.java which is why this file wouldnt apply cleanly with the
earlier patch. I merged my changes and am attaching a new patch (Derby928.3.diff.txt). Please
take a look.

The only changes in Derby928.3.diff.txt compared to the earlier Derby928.v2.diff.txt is
-- Added comment to link to DERBY-928 html table and also comments to runtest. Also enhanced
test to avoid case of DERBY-300.
-- made one master file for both DerbyNet and DerbyNetClient for sysinfo_withproperties.out


Ran derbynet/testSecMec.java with classes on ibm131/ibm141/ibm142/ibm15/jdk131/jdk141/jdk15/jdk142
OK.
Ran derbynetclientmats and derbynetmats on linux/ibm142 ok (with known failures)

Thanks. 

> Add ability to network server to accept connections with a certain security mechanism.
> --------------------------------------------------------------------------------------
>
>          Key: DERBY-928
>          URL: http://issues.apache.org/jira/browse/DERBY-928
>      Project: Derby
>         Type: New Feature
>   Components: Network Server
>     Reporter: Sunitha Kambhampati
>     Assignee: Sunitha Kambhampati
>      Fix For: 10.2.0.0
>  Attachments: Derby928.3.diff.txt, Derby928.3.stat.txt, Derby928.diff.txt, Derby928.stat.txt,
Derby928_Table_SecurityMechanisms..htm, Derby928_v2_diff.txt, Derby928_v2_stat.txt
>
> Currently the network server has support for the following security mechanisms
> 1) USRIDONL (userid only),
> 2) USRIDPWD (clear text userid and password),
> 3) EUSRIDPWD (encrypted userid and password).
> Thus the #3 encrypted userid and password security mechanism is secure with respect to
the userid/password sent across the wire.  Currently there is no way to setup the network
server to ensure that it accepts connections coming in at a certain security mechanism.  
It seems reasonable & useful to have a server want to accept connections from clients
with a particular security mechanism (e.g  lets say encrypted userid/password and reject usridpwd
ie clear text userid and password)
> This jira will add support for this by adding a property to enable the server to be able
to accept connections from clients with a certain security mechanism.
> --------------------
> I actually couldnt find if a rank was given to the security mechanisms in the drda spec.
 If it were so, then maybe a property for setting the minimum security mechanism accepted
by the server would be appropriate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message