Skip to main content

Hudson and WebSphere

It has been a while I have been playing with Hudson. It is way better than any other integration server I have seen and is crazily simple to extend. I'd love to use it at work but for the moment we are still stucked with Cruise Control. Said that, I think the integration with the "WebSphere world" can be kind of improved.
I mean Hudson war file can be installed on WAS; moreover there are already few WebSphere/IBM plugins as the WAS Builder and the RAD Builder. But either these than the out of the box deploy plugin don't support any WebSphere server. The WAS Builder plugin allow you to deploy on WebSphere but for what I undestood you need to write your own script.
I know WebSphere is a proprietary product and is a kind of closed world, and WAS itself has been defined from Hudson users "exhotic" but, being working with WebSphere for a while, and predicting I'll be working with it for yet another while, I'd like to have an out of the box mechanism to deploy the artifacts to WAS and even WebSphere Portal. Being this not existing at the moment I did decide to write it myself. :)
The solution will be havily JMX based and I am taking freely hints from the java file here.
At the moment, until I undestand if I can extend the already existing plugin, I am going toward this direction as you can see from the picture below:


otherwise I will start my own plugin.
My plan is to build up the complete solution in 3 steps:

  1. release the WebSphere deploy plugin for WebSphere Application Server 6.1/7 (with security disabled)
  2. release the WebSphere deploy plugin for WebSphere Application Server 6.1/7 (with security enabled)
  3. release the WebSphere deploy plugin for WebSphere Portal Server 6.1
The steps 2 and 3 might have some extra complication due to some extra proprietary IBM jar files needed and moreover, for be able the plugin to work, an IBM JRE is needed.
I did decided to push these extra complication back and focus on the point 1 for the moment that seems "easier".
I should say I am not really far away to have a "golden candidate", I just need to undestand the gotcha relative to extending the existing plugin. So what to say, if you are a WebSphere and Hudson user waiting for a mechanism to deploy your build artifacts with an out of the box solution to WAS 6.1/7 and WPS 6.1 stay tuned!!

Antonio

Comments

Popular posts from this blog

OpenSSL Key Recovery Attack on DH small subgroups (CVE-2016-0701)

Usual Mandatory Disclaimer: IANAC (I am not a cryptographer) so I might likely end up writing a bunch of mistakes in this blog post...

tl;dr The OpenSSL 1.0.2 releases suffer from a Key Recovery Attack on DH small subgroups. This issue got assigned CVE-2016-0701 with a severity of High and OpenSSL 1.0.2 users should upgrade to 1.0.2f. If an application is using DH configured with parameters based on primes that are not "safe" or not Lim-Lee (as the one in RFC 5114) and either Static DH ciphersuites are used or DHE ciphersuites with the default OpenSSL configuration (in particular SSL_OP_SINGLE_DH_USE is not set) then is vulnerable to this attack.  It is believed that many popular applications (e.g. Apache mod_ssl) do set the  SSL_OP_SINGLE_DH_USE option and would therefore not be at risk (for DHE ciphersuites), they still might be for Static DH ciphersuites.
Introduction So if you are still here it means you wanna know more. And here is the thing. In my last blog post I was …

All your Paypal OAuth tokens belong to me - localhost for the win

tl;dr  I was able to hijack the OAuth tokens of EVERYPaypal OAuth application with a really simple trick.
Introduction If you have been following this blog you might have got tired of how many times  I have stressed out the importance of the redirect_uri parameter in the OAuth flow.
This simple parameter might be source of many headaches for any maintainer of OAuth installations being it a client or a server.
Accepting the risk of repeating myself here is two simple suggestions that may help you stay away from troubles (you can always skip this part and going directly to the Paypal Vulnerability section):
If you are building an OAuth client,   Thou shall register a redirect_uri as much as specific as you can
i.e. if your OAuth client callback is https://yourouauthclient.com/oauth/oauthprovider/callback then

DO register https://yourouauthclient.com/oauth/oauthprovider/callbackNOT JUST https://yourouauthclient.com/ or https://yourouauthclient.com/oauth If you are still not convinced here…

Critical vulnerability in JSON Web Encryption (JWE) - RFC 7516

tl;dr if you are using go-jose, node-jose, jose2go, Nimbus JOSE+JWT or jose4j with ECDH-ES please update to the latest version. RFC 7516 aka JSON Web Encryption (JWE) hence many software libraries implementing this specification used to suffer from a classic Invalid Curve Attack. This would allow an attacker to completely recover the secret key of a party using JWE with Key Agreement with Elliptic Curve Diffie-Hellman Ephemeral Static (ECDH-ES), where the sender could extract receiver’s private key.

Premise
In this blog post I assume you are already knowledgeable about elliptic curves and their use in cryptography. If not Nick Sullivan's A (Relatively Easy To Understand) Primer on Elliptic Curve Cryptography or Andrea Corbellini's series Elliptic Curve Cryptography: finite fields and discrete logarithms are great starting points. Then if you further want to climb the elliptic learning curve including the related attacks you might also want to visit https://safecurves.cr.yp.to…