Hi Mark,   
   With a little help from Janis I managed to fix that error with a correct   
   symlink. All is good on my Ubuntu machine now. On to the next phase... lol   
   Thanks,   
   Rich   
      
   > On Sat, 02 Nov 2013, Rich Ringer wrote to Mark Lewis:   
   > [ugh! top posting corrected to inline and quote initials fixed]   
   >> On Fri, 01 Nov 2013, Rich Ringer wrote to All:   
   >>> So I'm setting up BBBS under Ubuntu 13.10 32bit. I put my reg key   
   >>> in the BBBS directory and upgraded BBBS to the newest version. I   
   >>> run bbbsd and get this error:   
   >>> ./bbbsd: error while loading shared libraries: libcrypto.so.10:   
   >>> cannot open shared object file: No such file or directory   
   >>> When I use apt-get to install the package it tells me I'm already   
   >>> running the newest version...   
   >> run "locate libcrypto" and see what you find... all we're interested   
   >> in is the version numbers...   
   >> This is what I get:   
   >> /lib/i386-linux-gnu/libcrypto.so.0.9.8   
   >> /lib/i386-linux-gnu/libcrypto.so.1.0.0   
   >> /usr/lib/i386-linux-gnu/libcrypto.so.0.9.8   
   >yeah, that's what i thought... your *nix has libcrypto 0.9.8 and 1.0.0 but you   
   > bbbs is looking for libcrypto 10 as i mentioned previously...   
   >> what i'm thinking is that your bbbs is looking for 10 but your   
   >> system has 10.x or higher installed... how to handle this is   
   >> another matter, though... you do not want to downgrade libcrypto...   
   >> that's for sure... that means that bbbs needs to be built against   
   >> the newer version or it needs to be built monothicly (all libraries   
   >> in the executable instead of using external so libraries)...   
   > yeah... a quick google turns up this link   
   >http://askubuntu.com/questions/339364/libssl-so-10-cannot-open-shared-object-f   
   > le-no-such-file-or-directory   
   > short version: http://tinyurl.com/jvpchj9   
   > which has the following as an answer...   
   > [quote="Hugo Vieira"]   
   >> Lets make sure that you have your SSL installed and updated:   
   >>    
   >> sudo apt-get update   
   >> sudo apt-get install libssl1.0.0 libssl-dev   
   > HV   
   >> Now lets fix the naming of the file by creating a link:   
   >>    
   >> sudo ln -s /lib/x86_64-linux-gnu/libssl.so.1.0.0 /usr/lib/libssl.so.10   
   >>    
   >> And finally, lets inform the developer about this flaw so he can   
   >> fix it :)   
   > [/quote]   
   > seeing that your system already has libcrypto.so.1.0.0 installed, i will make   
   > an educated guess that you also have the above mentioned libssl installed...   
   >with that in mind, i would suggest creating a softlink similar to the above...   
   > sudo ln -s /lib/i386-linux-gnu/libcrypto.so.1.0.0 /usr/lib/libcrypto.so.10   
   > AND/OR   
   > sudo ln -s /lib/i386-linux-gnu/libcrypto.so.1.0.0   
   > /usr/lib/i386-linux-gnu/libcrypto.so.10   
   > [watch the wordwrap on that last line!]   
   > if this doesn't work for you, you can delete the one (or two) softlinks we   
   > created so your system is not cluttered up with them which may cause problems   
   > later...   
   > sudo rm /usr/lib/libcrypto.so.10   
   > AND/OR   
   > sudo rm /usr/lib/i386-linux-gnu/libcrypto.so.10   
   > either way, the maintainer still needs to be informed of the problem so they   
   > can correct it so that others don't have to dance this dance ;)   
   > NOTE: if you want to, you can verify your libssl with "locate libssl" in the   
   > same way that we did with libcrypto ;)   
   > )\/(ark   
      
   --- BBBS/NT v4.10 Dada-1   
    * Origin: Outpost Sierra VI (1:322/762)