<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: jbailo</title><link>https://news.ycombinator.com/user?id=jbailo</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 30 Apr 2026 20:35:54 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=jbailo" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by jbailo in "The Heartbleed Bug"]]></title><description><![CDATA[
<p>I used the OpenSSL library for building a SAML token parser in JBoss (java).   All the front end stuff was java and OpenSSL was used for public/private key decryption and validation of SAML tokens and signatures.  I'm not sure exactly what an OpenSSL "server" -- it sounds like there is a feature which you can implement (or not) in your webserver to test the SSL/TLS listener.<p>However, you could -- as I did -- use anything else as your interface for the web.  Why would you specifically include a heartbeat for just SSL is beyond me.   If a website is up and running, you'll know it with the usual methods, the https codes.   You don't need a separate "heartbeat" for telling you that an internal mechanism for processing a protocol is running...do you?</p>
]]></description><pubDate>Thu, 10 Apr 2014 04:09:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=7564137</link><dc:creator>jbailo</dc:creator><comments>https://news.ycombinator.com/item?id=7564137</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=7564137</guid></item></channel></rss>