No usable version of libssl was found

[pieter-bos]

Hello! I recently updated my computer, and carbon now forwards this message from Boogie:

carbon 1.0
carbon found 1 error in 1.95s:
  [0] An internal error occurred. Found an unparsable output from Boogie: No usable version of libssl was found (<no position>)

Indeed, running boogie results in the same message:

$ ./Boogie 
No usable version of libssl was found
Aborted (core dumped)

This is with the boogie that is distributed with the viper release (2022.2).

Looking at strace it seems Boogie is expecting libssl version 1.0/1.1, which is no longer included with my distribution (Ubuntu 22.04), I can only easily install libssl3. I think viper's boogie is built with .net 3.1, which expects libssl1 and not 3 (see also here).

Pratically I would suggest to either:

• Update to .NET 6+, since .NET 3.1 will be EOL in december anyway, or;
• Distribute libssl1.1 with Boogie

In case anyone encounters this issue and wants a hacky workaround, it seems installing libssl1.1 is the only action required, e.g. for ubuntu from the previous LTS

[gauravpartha]

Thanks a lot for the information and the temporary workaround. I don't think the (fairly old) Boogie version we are working with is compatible with .NET 6 (although there would only be minimal changes required to Boogie). Ideally, we would update to the newest Boogie version. One thing making this update somewhat nontrivial is that the Carbon counterexamples feature breaks down with the newest Boogie version and requires some changes on the Carbon side.

[gauravpartha]

We have upgraded Carbon to use Boogie 2.15.9 in the merged PR #441, which is based on .NET 6. So, this problem should hopefully be solved.