It's possible that libcrypto is not tied to the normal curl4 or openssl on your distro like it is in Ubuntu.

Try

sudo apt install libcrypto

For boinccmd try:

./boinccmd --project_attach http://setiathome.berkeley.edu <weak key>

E: Unable to locate package libcrypto

can't connect to local host

---

Radjin~

Sounds like you haven’t set the boinccmd to be executable.

Run chmod +x on it.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

It's possible that libcrypto is not tied to the normal curl4 or openssl on your distro like it is in Ubuntu.

Try

sudo apt install libcrypto

For boinccmd try:

./boinccmd --project_attach http://setiathome.berkeley.edu <weak key>

E: Unable to locate package libcrypto

can't connect to local host

Yes, the openssl should have brought in the libcrypto on its own. Since you say you have openssl already installed, I don't have much more to offer. You will have to consult your distro help community.

keith@Serenity:~$ apt show libssl1.1 -a
Package: libssl1.1
Version: 1.1.1-1ubuntu2.1~18.04.4
Priority: important
Section: libs
Source: openssl
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian OpenSSL Team <pkg-openssl-devel@lists.alioth.debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 4,027 kB
Depends: libc6 (>= 2.25), debconf (>= 0.5) | debconf-2.0
Breaks: isync (<= 1.3.0-1build1), python-boto (<= 2.44.0-1ubuntu2), python-httplib2 (<= 0.9.2+dfsg-1), python-imaplib2 (<= 2.57-1), python3-boto (<= 2.44.0-1ubuntu2), python3-imaplib2 (<= 2.57-1)
Homepage: https://www.openssl.org/
Task: minimal
Supported: 5y
Download-Size: 1,300 kB
APT-Manual-Installed: yes
APT-Sources: http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
Description: Secure Sockets Layer toolkit - shared libraries
This package is part of the OpenSSL project's implementation of the SSL
and TLS cryptographic protocols for secure communication over the
Internet.
.
It provides the libssl and libcrypto shared libraries.

Package: libssl1.1
Version: 1.1.0g-2ubuntu4
Priority: important
Section: libs
Source: openssl
Origin: Ubuntu
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian OpenSSL Team <pkg-openssl-devel@lists.alioth.debian.org>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 3,493 kB
Depends: libc6 (>= 2.14), debconf (>= 0.5) | debconf-2.0
Breaks: salt-common (<= 2016.3.3+ds-3)
Homepage: https://www.openssl.org/
Task: minimal
Supported: 5y
Download-Size: 1,128 kB
APT-Sources: http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Description: Secure Sockets Layer toolkit - shared libraries
This package is part of the OpenSSL project's implementation of the SSL
and TLS cryptographic protocols for secure communication over the
Internet.
.
It provides the libssl and libcrypto shared libraries.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Also it could be possible that your version of ssl is too high and the special app is looking specifically for 1.0.0. You have 1.1.1.

Try installing OpenSSL-1.0.0

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

Also it could be possible that your version of ssl is too high and the special app is looking specifically for 1.0.0. You have 1.1.1.

Try installing OpenSSL-1.0.0

Didn't think of that. If you can't install the older OpenSSL-1.0.0, then you can try making a linked file to the expected filename from your OpenSSL-1.1.1c library.

If Ian's suggestion does not work try this next. The paths to the normal directories are for my Ubuntu 18.04.3. Don't know if they are the same in Debian 10. Adjust as needed.

ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.1 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0

ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Sounds like you haven’t set the boinccmd to be executable.

Run chmod +x on it.

At least I didn't get an error on this.

I still get the following though...


boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
-bash: boinccmd: command not found

./boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
can't connect to local host

Could this be connected the the missing or mismatched libraries?

---

Radjin~

Is the boinc file set to executable also? It should be.

chmod +x boinc

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

This is why I previously mentioned that the dependencies can become a real headache with some distros. I've spent hours doing these same drills. Sometimes I was finally able to force it to work, and other times I just had to give up and cut my time losses. Technically, you should be able to get it to work on any Linux distro, but the question is how much time you will need to invest. My lesson learned from the testing I conducted: Stick with the distros that are known to work and have strong support from the SETI/BOINC community here.

I hope you're able to get the Debian 10 distro sorted. Good luck.

Sounds like you haven’t set the boinccmd to be executable.

Run chmod +x on it.

At least I didn't get an error on this.

I still get the following though...


boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
-bash: boinccmd: command not found

./boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
can't connect to local host

Could this be connected the the missing or mismatched libraries?

Since the client won't run with the missing dependencies, there is nobody home for boinccmd to talk to.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

This is why I previously mentioned that the dependencies can become a real headache with some distros. I've spent hours doing these same drills. Sometimes I was finally able to force it to work, and other times I just had to give up and cut my time losses. Technically, you should be able to get it to work on any Linux distro, but the question is how much time you will need to invest. My lesson learned from the testing I conducted: Stick with the distros that are known to work and have strong support from the SETI/BOINC community here.

I hope you're able to get the Debian 10 distro sorted. Good luck.

Thanks...

This has been a stable and simple web server, I just thought I would do some good with the all the idle time it has. Your right though, at some point it becomes too much to or too in-depth and I would hate t break what I have running so well.

---

Radjin~

Is the boinc file set to executable also? It should be.

chmod +x boinc

I did this with and without sudo and still the same thing.

---

Radjin~

This has been a stable and simple web server, I just thought I would do some good with the all the idle time it has. Your right though, at some point it becomes too much to or too in-depth and I would hate t break what I have running so well.

Any reason you couldn't migrate the web server to an Ubuntu or Mint distro? Peppermint may also be a great choice for a webserver. All three of those distros will work with the AIO with no modifications needed.

Didn't think of that. If you can't install the older OpenSSL-1.0.0, then you can try making a linked file to the expected filename from your OpenSSL-1.1.1c library.

If Ian's suggestion does not work try this next. The paths to the normal directories are for my Ubuntu 18.04.3. Don't know if they are the same in Debian 10. Adjust as needed.

ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.1 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0

ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

Both of these went through without error but made no effect on the results. I even rebooted the system to be sure.

---

Radjin~

Didn't think of that. If you can't install the older OpenSSL-1.0.0, then you can try making a linked file to the expected filename from your OpenSSL-1.1.1c library.

If Ian's suggestion does not work try this next. The paths to the normal directories are for my Ubuntu 18.04.3. Don't know if they are the same in Debian 10. Adjust as needed.

ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.1 /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0

ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0

Both of these went through without error but made no effect on the results. I even rebooted the system to be sure.

Should have also said to run ldconfig after making the symbolic links, but the reboot would have picked up the new links anyway. So don't have any other suggestions other than give up or consult your Debian 10 community for help.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Thanks for the help.

---

Radjin~

Thanks for the help.

In the BOINC/docs folder there is an App Specifically Built for SSL 1.1. It's called boinc_for_Ubuntu_19.04.7z.
Simply Expand that file and move it to the top level Of the BOINC folder replacing the other boinc file as per the README 7.4.44 & 7.14.2 file.
There is another ReadMe in BOINC/projects/setiathome.berkeley.edu/docs for the CUDA App.

Thanks for the help.

In the BOINC/docs folder there is an App Specifically Built for SSL 1.1. It's called boinc_for_Ubuntu_19.04.7z.
Simply Expand that file and move it to the top level Of the BOINC folder replacing the other boinc file as per the README 7.4.44 & 7.14.2 file.
There is another ReadMe in BOINC/projects/setiathome.berkeley.edu/docs for the CUDA App.

A bit different reply:

~/boinc$ boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
-bash: /usr/bin/boinccmd: No such file or directory

~/boinc$ ./boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
can't connect to local host

---

Radjin~

The folder should be named BOINC, not boinc.

The folder should be named BOINC, not boinc.

I didn't know that made a difference but here is the results...


~/BOINC$ boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
-bash: /usr/bin/boinccmd: No such file or directory

~/BOINC$ ./boinccmd --project_attach http://setiathome.berkeley.edu <weak key>
can't connect to local host

---

Radjin~

Are you sure the boinc client is running on another terminal?

---