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

Slack SAML authentication bypass

tl;dr  I found a severe issue in the Slack's SAML implementation that allowed me to bypass the authentication. This has now been solved by Slack.
Introduction IMHO the rule #1 of any bug hunter (note I do not consider myself one of them since I do this really sporadically) is to have a good RSS feed list.  In the course of the last years I built a pretty decent one and I try to follow other security experts trying to "steal" some useful tricks. There are many experts in different fields of the security panorama and too many to quote them here (maybe another post). But one of the leading expert (that I follow) on SAML is by far Ioannis Kakavas. Indeed he was able in the last years to find serious vulnerability in the SAML implementation of Microsoft and Github. Usually I am more an "OAuth guy" but since both, SAML and OAuth, are nothing else that grandchildren of Kerberos learning SAML has been in my todo list for long time. The Github incident gave me the final…

Cross-origin brute-forcing of Github SAML and 2FA recovery codes

Yesterday while reading my Twitter stream I found this interesting article about  downloading GitHub SSO bypass codes. Same as Yasin Soliman I was invited to a Github pre-release of the organisation SAML single sign-on (SSO) private program. And same as him I found an issue in the same endpoint. So I thought to write a quick blog post about it. Github already published a tl;dr about this,



 I will try to fill the blanks here.

As mentioned by Yasin, Github offers an endpoint where privileged users can recover bypass codes. These recovery codes were accessible for download as plaintext and had the content-type as text/plain, something like:



What immediately caught my attention was that the format of the code forms (with some exceptions) a valid JavaScript file with lines in the format of XXXXX-XXXXX, ten hex digits separated by a hyphen. This is interpreted in JavaScript as the subtraction of two variables! This remember an old blog post of mine where I could possibly exfiltrate informa…

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…