<div dir="ltr">As you seem to know, the short answer is that you probably can't do it without breaking packaging, at least a li'l. The longer answer depends on what else is installed on the machine and reliant on OpenSSL. You'd ultimately have to compile from source. You could make a package from that compilation, and you could even set the version on the package to fool other packages into believing that it isn't the version that it is. Applications may well break, though. It all depends on the ones that you care about and how they operate. On the bright side, you're immune to Heartbleed!<div><br></div><div>Now, the obvious question: why not upgrade/migrate?</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Sep 5, 2015 at 11:27 AM, Sean LeBlanc <span dir="ltr"><<a href="mailto:seanleblanc@comcast.net" target="_blank">seanleblanc@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I was wondering if anyone here has any advice on upgrading OpenSSL on<br>
RHEL 5.6 w/o updating to a newer RHEL version (5.x or 6.x or something<br>
else)?<br>
<br>
It seems RHEL 5.6, at least w/o going off the vendor reservation, tracks<br>
0.9.8 something (e?), and RH backports security fixes, from what I can tell.<br>
<br>
It'd be nice to get TLS 1.2 especially, but I'm not sure how easy that<br>
is w/o doing a broader upgrade.<br>
<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</blockquote></div><br></div>