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

Billion Laugh Attack in https://sites.google.com

tl;dr https://sites.google.com suffered from a Billion Laugh Attack vulnerability that made the containerized environment to crash with a single invocation.
Introduction Few months ago I applied for a talk at a security conference titled Soyouwanna be a Bug Bounty Hunter but it was rejected :(. The reason behind it is that I have been on/off in the bug bounty business for a while as you can see here:
Funny. Found in a forgotten drawer from the time I was a bug hunter :p #facebook#bug#bountypic.twitter.com/Tt4saGZVLI — Antonio Sanso (@asanso) November 30, 2018 and I would have liked to share some of the things I have learned during these years (not necessary technical advises only). You can find a couple of these advises here:


Rule #1 of any bug hunter is to have a good RSS feed list
and here


The rule #2 of any bug hunter is to DO NOT be to fussy with 'food' specifically with "left over"
Today's rule is: The rule #3 of any bug hunter is DO LOOK at the old stuff

and…

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 …

Top 10 OAuth 2 Implementation Vulnerabilities

Some time ago I posted a blogpost abut  Top 5 OAuth 2 Implementation Vulnerabilities.
This week I have extended the list while presenting Top X OAuth 2 Hacks at OWASP Switzerland.

This blog post (like the presentation) is just a collection of interesting attack OAuth related.

#10 The Postman Always Rings Twice  I have introduced this 'attack' in last year post . This is for provider implementer, it is not extremely severe but, hey, is better to follow the spec. Specifically

The client MUST NOT use the authorization code  more than once.  If an authorization code is used more than once, the authorization server MUST deny the request and SHOULD revoke (when possible) all tokens previously issued based on that authorization code.

It turned out that even Facebook and Googledid it wrong... :)

#9 Match Point To all OAuth Providers be sure to follow section 4.1.3 of the spec in particular

...if the "redirect_uri" parameter was included in the initial authorization requ…