Hi, Thank you for your reply.
What makes me sorrow is for example this article on retroshare Version 0.5.4a_5582 :
http://www.gulli.com/news/19797-anonymi ... 2012-09-24 it states that this version of retroshare got an openssl library updated to version 1.0.1c.
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable, if it is not compiled with the -DOPENSSL_NO_HEARTBEATS option.
OpenSSL 1.0.1g is NOT vulnerable, OpenSSL 1.0.0 branch is NOT vulnerable, OpenSSL 0.9.8 branch is NOT vulnerable
If you make a google search with heartbeat retroshare, you find for example:
viewtopic.php?f=8&t=820 with entries like
"set heartbeat values to intermediate value"
This is for a very old retroshare version.
I am only a retroshare newbie, but what openssl version does the current retroshare use?
Wikipedia says it uses a modified version of openssl. I have not found the openssl library in the retroshare sourcecode yet. Perhaps retroshare relies on the system wide installed openssl library. But then certainly the windows installer ships with an openssl library. Does retroshare use the openssl library with the heartbeat option enabled? Does retroshare use the heartbeat option somehow?
Even if first tests say retroshare is not vulnerable, i still think that updating openssl (if it is shiped with retroshare somehow) would be a good thing to do,