Support for cert auth in JDBC

Started by Marc-André Laverdièreover 14 years ago4 messages
#1Marc-André Laverdière
marc-andre@atc.tcs.com

Hello developers,

My project had a requirement to use certificate authentication to the PG
server. Our application uses Hibernate.

We did just that and my boss has OKed a source release.

Now, the current version of the code has dependencies on our internal
libraries, so I'll need to spend a bit of time making this 'standard'
Java code.

Would you please tell me how you'd prefer for me to proceed to do that?
Do I need write access to your CVS repo, or should I just send the code
and test case by email?

Is there a specific version of the JDBC code you want me to work from,
should I just pick whatever is HEAD?

Any package you'd like me to choose?

Any specific crypto/ssl requirements to consider?

Any specific dependencies to use instead of others? (e.g. I like SLF4J,
but that's not everyone's choice...)

--
Marc-Andr� Laverdi�re
Software Security Scientist
Innovation Labs, Tata Consultancy Services
Hyderabad, India

#2Dave Cramer
pg@fastcrypt.com
In reply to: Marc-André Laverdière (#1)
Re: Support for cert auth in JDBC

Marc,

Please just send a cvs context diff from HEAD to the JDBC list.

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

2011/5/17 Marc-André Laverdière <marc-andre@atc.tcs.com>:

Show quoted text

Hello developers,

My project had a requirement to use certificate authentication to the PG
server. Our application uses Hibernate.

We did just that and my boss has OKed a source release.

Now, the current version of the code has dependencies on our internal
libraries, so I'll need to spend a bit of time making this 'standard'
Java code.

Would you please tell me how you'd prefer for me to proceed to do that?
Do I need write access to your CVS repo, or should I just send the code
and test case by email?

Is there a specific version of the JDBC code you want me to work from,
should I just pick whatever is HEAD?

Any package you'd like me to choose?

Any specific crypto/ssl requirements to consider?

Any specific dependencies to use instead of others? (e.g. I like SLF4J,
but that's not everyone's choice...)

--
Marc-André Laverdière
Software Security Scientist
Innovation Labs, Tata Consultancy Services
Hyderabad, India

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#3Stephen Frost
sfrost@snowman.net
In reply to: Marc-André Laverdière (#1)
Re: Support for cert auth in JDBC

Marc-André,

* Marc-André Laverdière (marc-andre@atc.tcs.com) wrote:

Would you please tell me how you'd prefer for me to proceed to do that?
Do I need write access to your CVS repo, or should I just send the code
and test case by email?

Ideally, you would submit the patch, as a context diff, to this mailing
list and then add the patch to our 'CommitFest' system:
http://commitfest.postgresql.org

There is quite a bit of additional guideance on what a patch should look
like, etc, here: http://wiki.postgresql.org/wiki/Submitting_a_Patch

Is there a specific version of the JDBC code you want me to work from,
should I just pick whatever is HEAD?

I'm not too familiar with the JDBC parts, you might post this question
to the JDBC mailing list.

Any specific crypto/ssl requirements to consider?

We currently use and pretty heavily depend on OpenSSL. I'm not sure how
much that matters when it comes to JDBC.

Thanks,

Stephen

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Stephen Frost (#3)
Re: Support for cert auth in JDBC

Stephen Frost <sfrost@snowman.net> writes:

Marc-Andr�,
* Marc-Andr� Laverdi�re (marc-andre@atc.tcs.com) wrote:

Would you please tell me how you'd prefer for me to proceed to do that?
Do I need write access to your CVS repo, or should I just send the code
and test case by email?

Ideally, you would submit the patch, as a context diff, to this mailing
list and then add the patch to our 'CommitFest' system:
http://commitfest.postgresql.org

It sounded to me like this was a patch against the JDBC driver, not the
core server, in which case the above advice would be incorrect. JDBC
is developed by a separate project. You should join the pgsql-jdbc
mailing list and send your patch there.

regards, tom lane