[GH-ISSUE #156] new version of libssh breaks barrier functionality

gitea-mirror commented

2026-05-05 05:19:36 -06:00

Owner

Originally created by @johnny-mac on GitHub (Oct 17, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/156

Hello. Been using Barrier for quite some time now, can't seem to figure out why it started doing this today... I've never had a problem with it til now, for some reason my client PCs don't want to connect to the server :/

I'm using Artix w runit (server and client) & Devuan Linux(client). Connection just doesn't seem to want to work, no idea why.... It seems to be cutting in and out or something... I really have no idea what might be causing this issue.

Originally created by @johnny-mac on GitHub (Oct 17, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/156 Hello. Been using Barrier for quite some time now, can't seem to figure out why it started doing this today... I've never had a problem with it til now, for some reason my client PCs don't want to connect to the server :/ I'm using Artix w runit (server and client) & Devuan Linux(client). Connection just doesn't seem to want to work, no idea why.... It seems to be cutting in and out or something... I really have no idea what might be causing this issue.

gitea-mirror

2026-05-05 05:19:36 -06:00

closed this issue
added the
linux
label

gitea-mirror commented

2026-05-05 05:19:40 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 17, 2018):

Weird... I've noticed that if I try to SSH to one of my client PCs that it just starts to work.... :/ doesn't make much sense to me.... IDK, maybe a dependency got updated recently & is causing barrier to bug out?
Sorry I can't provide you with anything else, not sure what is relevant to this issue.

@johnny-mac commented on GitHub (Oct 17, 2018): Weird... I've noticed that if I try to SSH to one of my client PCs that it just starts to work.... :/ doesn't make much sense to me.... IDK, maybe a dependency got updated recently & is causing barrier to bug out? Sorry I can't provide you with anything else, not sure what is relevant to this issue.

gitea-mirror commented

2026-05-05 05:19:45 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 17, 2018):

This may not be related to Barrier, I'm not really sure yet.... I think libssh might have something to do with it. What are the odds that libssh just got updated & now this is happening? O.o

attica-5.51.0-1-x86_64.pkg.tar.xz            kcompletion-5.51.0-1-x86_64.pkg.tar.xz      kio-5.51.0-1-x86_64.pkg.tar.xz              kxmlgui-5.51.0-1-x86_64.pkg.tar.xz                  net-snmp-5.8-1-x86_64.pkg.tar.xz
babl-0.1.58-1-x86_64.pkg.tar.xz              kconfig-5.51.0-1-x86_64.pkg.tar.xz          kitemmodels-5.51.0-1-x86_64.pkg.tar.xz      lib32-glibc-2.28-5-x86_64.pkg.tar.xz                nvidia-dkms-410.57-6-x86_64.pkg.tar.xz
bluez-qt-5.51.0-1-x86_64.pkg.tar.xz          kconfigwidgets-5.51.0-1-x86_64.pkg.tar.xz   kitemviews-5.51.0-1-x86_64.pkg.tar.xz       lib32-libdrm-2.4.96-1-x86_64.pkg.tar.xz             openal-1.19.1-1-x86_64.pkg.tar.xz
breeze-icons-5.51.0-1-any.pkg.tar.xz         kcoreaddons-5.51.0-1-x86_64.pkg.tar.xz      kjobwidgets-5.51.0-1-x86_64.pkg.tar.xz      lib32-libsm-1.2.3-1-x86_64.pkg.tar.xz               oxygen-icons-1:5.51.0-1-any.pkg.tar.xz
cython-0.29-1-x86_64.pkg.tar.xz              kcrash-5.51.0-1-x86_64.pkg.tar.xz           kjs-5.51.0-1-x86_64.pkg.tar.xz              lib32-libx11-1.6.7-1-x86_64.pkg.tar.xz              purpose-5.51.0-1-x86_64.pkg.tar.xz
cython2-0.29-1-x86_64.pkg.tar.xz             kdbusaddons-5.51.0-1-x86_64.pkg.tar.xz      knewstuff-5.51.0-1-x86_64.pkg.tar.xz        libdrm-2.4.96-1-x86_64.pkg.tar.xz                   sane-1.0.27-2-x86_64.pkg.tar.xz
extra-cmake-modules-5.51.0-1-any.pkg.tar.xz  kdeclarative-5.51.0-1-x86_64.pkg.tar.xz     knotifications-5.51.0-1-x86_64.pkg.tar.xz   libgit2-1:0.27.5-1-x86_64.pkg.tar.xz                sfml-2.5.1-1-x86_64.pkg.tar.xz
gdb-8.2-2.1-x86_64.pkg.tar.xz                kded-5.51.0-1-x86_64.pkg.tar.xz             knotifyconfig-5.51.0-1-x86_64.pkg.tar.xz    libkscreen-5.14.1-1-x86_64.pkg.tar.xz               solid-5.51.0-1-x86_64.pkg.tar.xz
gdb-common-8.2-2.1-x86_64.pkg.tar.xz         kdelibs4support-5.51.0-1-x86_64.pkg.tar.xz  kpackage-5.51.0-1-x86_64.pkg.tar.xz         libsm-1.2.3-1-x86_64.pkg.tar.xz                     sonnet-5.51.0-1-x86_64.pkg.tar.xz
glibc-2.28-5-x86_64.pkg.tar.xz               kemoticons-5.51.0-1-x86_64.pkg.tar.xz       kparts-5.51.0-1-x86_64.pkg.tar.xz           libssh-0.8.4-1-x86_64.pkg.tar.xz                    telegram-desktop-1.4.3-1-x86_64.pkg.tar.xz
grub-customizer-5.1.0-1-x86_64.pkg.tar.xz    kfilemetadata-5.51.0-1-x86_64.pkg.tar.xz    kross-5.51.0-1-x86_64.pkg.tar.xz            linux-4.18.14.artix1-1-x86_64.pkg.tar.xz            texinfo-6.5-2-x86_64.pkg.tar.xz
hplip-1:3.18.6-2-x86_64.pkg.tar.xz           kglobalaccel-5.51.0-1-x86_64.pkg.tar.xz     kservice-5.51.0-1-x86_64.pkg.tar.xz         linux-headers-4.18.14.artix1-1-x86_64.pkg.tar.xz    vhba-module-dkms-20170610-107-x86_64.pkg.tar.xz
kactivities-5.51.0-1-x86_64.pkg.tar.xz       kguiaddons-5.51.0-1-x86_64.pkg.tar.xz       ktextwidgets-5.51.0-1-x86_64.pkg.tar.xz     linux-zen-4.18.14.zen1-1-x86_64.pkg.tar.xz          wine-3.18-1-x86_64.pkg.tar.xz
karchive-5.51.0-1-x86_64.pkg.tar.xz          khtml-5.51.0-1-x86_64.pkg.tar.xz            kunitconversion-5.51.0-1-x86_64.pkg.tar.xz  linux-zen-headers-4.18.14.zen1-1-x86_64.pkg.tar.xz  wiredtiger-3.1.0.20180920-1-x86_64.pkg.tar.xz
kauth-5.51.0-1-x86_64.pkg.tar.xz             ki18n-5.51.0-1-x86_64.pkg.tar.xz            kwallet-5.51.0-1-x86_64.pkg.tar.xz          lxpanel-0.9.3-2-x86_64.pkg.tar.xz                   zstd-1.3.6-1-x86_64.pkg.tar.xz
kbookmarks-5.51.0-1-x86_64.pkg.tar.xz        kiconthemes-5.51.0-1-x86_64.pkg.tar.xz      kwayland-5.51.0-1-x86_64.pkg.tar.xz         mkinitcpio-24-3-any.pkg.tar.xz
kcmutils-5.51.0-1-x86_64.pkg.tar.xz          kidletime-5.51.0-1-x86_64.pkg.tar.xz        kwidgetsaddons-5.51.0-1-x86_64.pkg.tar.xz   mongodb-4.0.3-1-x86_64.pkg.tar.xz
kcodecs-5.51.0-1-x86_64.pkg.tar.xz           kinit-5.51.0-1-x86_64.pkg.tar.xz            kwindowsystem-5.51.0-1-x86_64.pkg.tar.xz    ncurses-6.1-4-x86_64.pkg.tar.xz

@johnny-mac commented on GitHub (Oct 17, 2018): This may not be related to Barrier, I'm not really sure yet.... I think libssh might have something to do with it. What are the odds that libssh just got updated & now this is happening? O.o ``` attica-5.51.0-1-x86_64.pkg.tar.xz kcompletion-5.51.0-1-x86_64.pkg.tar.xz kio-5.51.0-1-x86_64.pkg.tar.xz kxmlgui-5.51.0-1-x86_64.pkg.tar.xz net-snmp-5.8-1-x86_64.pkg.tar.xz babl-0.1.58-1-x86_64.pkg.tar.xz kconfig-5.51.0-1-x86_64.pkg.tar.xz kitemmodels-5.51.0-1-x86_64.pkg.tar.xz lib32-glibc-2.28-5-x86_64.pkg.tar.xz nvidia-dkms-410.57-6-x86_64.pkg.tar.xz bluez-qt-5.51.0-1-x86_64.pkg.tar.xz kconfigwidgets-5.51.0-1-x86_64.pkg.tar.xz kitemviews-5.51.0-1-x86_64.pkg.tar.xz lib32-libdrm-2.4.96-1-x86_64.pkg.tar.xz openal-1.19.1-1-x86_64.pkg.tar.xz breeze-icons-5.51.0-1-any.pkg.tar.xz kcoreaddons-5.51.0-1-x86_64.pkg.tar.xz kjobwidgets-5.51.0-1-x86_64.pkg.tar.xz lib32-libsm-1.2.3-1-x86_64.pkg.tar.xz oxygen-icons-1:5.51.0-1-any.pkg.tar.xz cython-0.29-1-x86_64.pkg.tar.xz kcrash-5.51.0-1-x86_64.pkg.tar.xz kjs-5.51.0-1-x86_64.pkg.tar.xz lib32-libx11-1.6.7-1-x86_64.pkg.tar.xz purpose-5.51.0-1-x86_64.pkg.tar.xz cython2-0.29-1-x86_64.pkg.tar.xz kdbusaddons-5.51.0-1-x86_64.pkg.tar.xz knewstuff-5.51.0-1-x86_64.pkg.tar.xz libdrm-2.4.96-1-x86_64.pkg.tar.xz sane-1.0.27-2-x86_64.pkg.tar.xz extra-cmake-modules-5.51.0-1-any.pkg.tar.xz kdeclarative-5.51.0-1-x86_64.pkg.tar.xz knotifications-5.51.0-1-x86_64.pkg.tar.xz libgit2-1:0.27.5-1-x86_64.pkg.tar.xz sfml-2.5.1-1-x86_64.pkg.tar.xz gdb-8.2-2.1-x86_64.pkg.tar.xz kded-5.51.0-1-x86_64.pkg.tar.xz knotifyconfig-5.51.0-1-x86_64.pkg.tar.xz libkscreen-5.14.1-1-x86_64.pkg.tar.xz solid-5.51.0-1-x86_64.pkg.tar.xz gdb-common-8.2-2.1-x86_64.pkg.tar.xz kdelibs4support-5.51.0-1-x86_64.pkg.tar.xz kpackage-5.51.0-1-x86_64.pkg.tar.xz libsm-1.2.3-1-x86_64.pkg.tar.xz sonnet-5.51.0-1-x86_64.pkg.tar.xz glibc-2.28-5-x86_64.pkg.tar.xz kemoticons-5.51.0-1-x86_64.pkg.tar.xz kparts-5.51.0-1-x86_64.pkg.tar.xz libssh-0.8.4-1-x86_64.pkg.tar.xz telegram-desktop-1.4.3-1-x86_64.pkg.tar.xz grub-customizer-5.1.0-1-x86_64.pkg.tar.xz kfilemetadata-5.51.0-1-x86_64.pkg.tar.xz kross-5.51.0-1-x86_64.pkg.tar.xz linux-4.18.14.artix1-1-x86_64.pkg.tar.xz texinfo-6.5-2-x86_64.pkg.tar.xz hplip-1:3.18.6-2-x86_64.pkg.tar.xz kglobalaccel-5.51.0-1-x86_64.pkg.tar.xz kservice-5.51.0-1-x86_64.pkg.tar.xz linux-headers-4.18.14.artix1-1-x86_64.pkg.tar.xz vhba-module-dkms-20170610-107-x86_64.pkg.tar.xz kactivities-5.51.0-1-x86_64.pkg.tar.xz kguiaddons-5.51.0-1-x86_64.pkg.tar.xz ktextwidgets-5.51.0-1-x86_64.pkg.tar.xz linux-zen-4.18.14.zen1-1-x86_64.pkg.tar.xz wine-3.18-1-x86_64.pkg.tar.xz karchive-5.51.0-1-x86_64.pkg.tar.xz khtml-5.51.0-1-x86_64.pkg.tar.xz kunitconversion-5.51.0-1-x86_64.pkg.tar.xz linux-zen-headers-4.18.14.zen1-1-x86_64.pkg.tar.xz wiredtiger-3.1.0.20180920-1-x86_64.pkg.tar.xz kauth-5.51.0-1-x86_64.pkg.tar.xz ki18n-5.51.0-1-x86_64.pkg.tar.xz kwallet-5.51.0-1-x86_64.pkg.tar.xz lxpanel-0.9.3-2-x86_64.pkg.tar.xz zstd-1.3.6-1-x86_64.pkg.tar.xz kbookmarks-5.51.0-1-x86_64.pkg.tar.xz kiconthemes-5.51.0-1-x86_64.pkg.tar.xz kwayland-5.51.0-1-x86_64.pkg.tar.xz mkinitcpio-24-3-any.pkg.tar.xz kcmutils-5.51.0-1-x86_64.pkg.tar.xz kidletime-5.51.0-1-x86_64.pkg.tar.xz kwidgetsaddons-5.51.0-1-x86_64.pkg.tar.xz mongodb-4.0.3-1-x86_64.pkg.tar.xz kcodecs-5.51.0-1-x86_64.pkg.tar.xz kinit-5.51.0-1-x86_64.pkg.tar.xz kwindowsystem-5.51.0-1-x86_64.pkg.tar.xz ncurses-6.1-4-x86_64.pkg.tar.xz ```

gitea-mirror commented

2026-05-05 05:19:49 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 17, 2018):

Yep! It would appear libssh was the culprit! So not barrier-related, but it definitely breaks barrier's functionality. Here's a PKGBUILD for the previous version of libssh(I just changed the version and it worked):

pkgbase=libssh
pkgname=(libssh libssh-docs)
pkgver=0.8.3
pkgrel=2
pkgdesc="Library for accessing ssh client services through C libraries"
url="http://www.libssh.org/"
license=(LGPL)
arch=(x86_64)
depends=(zlib openssl)
makedepends=(cmake cmocka doxygen python)
source=(https://www.libssh.org/files/${pkgver%.*}/$pkgname-$pkgver.tar.xz{,.asc})
sha256sums=('SKIP'
            'SKIP')
validpgpkeys=('8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D') # Andreas Schneider <asn@cryptomilk.org>

prepare() {
  # disable the test. It is confused by our clean container setup.
  # 'extra-x86-build' uses user 'nobody' that has a record in /etc/passwd file
  # but $HOME envvar is set to '/build'. The test expects that $HOME corresponds to passwd file.
  sed 's/cmocka_unit_test(torture_path_expand_tilde_unix),//' -i libssh-${pkgver}/tests/unittests/torture_misc.c

  mkdir -p build
}

build() {
  cd build
  cmake ../$pkgname-$pkgver \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DWITH_GSSAPI=OFF \
    -DUNIT_TESTING=ON
  make -j19
  make docs
}

check() {
  cd build
  make test
}

package_libssh() {
  cd build
  make DESTDIR="$pkgdir" install
}

package_libssh-docs() {
  pkgdesc="Documentation for libssh"
  depends=()

  mkdir -p "$pkgdir"/usr/share/doc/libssh
  cp -r build/doc/html "$pkgdir"/usr/share/doc/libssh
}

@johnny-mac commented on GitHub (Oct 17, 2018): Yep! It would appear libssh was the culprit! So not barrier-related, but it definitely breaks barrier's functionality. Here's a PKGBUILD for the previous version of libssh(I just changed the version and it worked): ``` pkgbase=libssh pkgname=(libssh libssh-docs) pkgver=0.8.3 pkgrel=2 pkgdesc="Library for accessing ssh client services through C libraries" url="http://www.libssh.org/" license=(LGPL) arch=(x86_64) depends=(zlib openssl) makedepends=(cmake cmocka doxygen python) source=(https://www.libssh.org/files/${pkgver%.*}/$pkgname-$pkgver.tar.xz{,.asc}) sha256sums=('SKIP' 'SKIP') validpgpkeys=('8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D') # Andreas Schneider <asn@cryptomilk.org> prepare() { # disable the test. It is confused by our clean container setup. # 'extra-x86-build' uses user 'nobody' that has a record in /etc/passwd file # but $HOME envvar is set to '/build'. The test expects that $HOME corresponds to passwd file. sed 's/cmocka_unit_test(torture_path_expand_tilde_unix),//' -i libssh-${pkgver}/tests/unittests/torture_misc.c mkdir -p build } build() { cd build cmake ../$pkgname-$pkgver \ -DCMAKE_INSTALL_PREFIX=/usr \ -DWITH_GSSAPI=OFF \ -DUNIT_TESTING=ON make -j19 make docs } check() { cd build make test } package_libssh() { cd build make DESTDIR="$pkgdir" install } package_libssh-docs() { pkgdesc="Documentation for libssh" depends=() mkdir -p "$pkgdir"/usr/share/doc/libssh cp -r build/doc/html "$pkgdir"/usr/share/doc/libssh } ```

gitea-mirror commented

2026-05-05 05:19:52 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Oct 17, 2018):

I don't think libssh is used in barrier at all, don't see why it would make an impact.

@AdrianKoshka commented on GitHub (Oct 17, 2018): I don't think libssh is used in barrier at all, don't see why it would make an impact.

gitea-mirror commented

2026-05-05 05:19:55 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 17, 2018):

It definitely appeared like that's what the problem was. I downgraded the package and now its all ok...
I could probably reproduce the problem if I upgraded libssh

@johnny-mac commented on GitHub (Oct 17, 2018): It definitely appeared like that's what the problem was. I downgraded the package and now its all ok... I could probably reproduce the problem if I upgraded libssh

gitea-mirror commented

2026-05-05 05:19:57 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Oct 17, 2018):

I'm no CMake expert, but I see no reference to libssh here. https://github.com/debauchee/barrier/blob/master/CMakeLists.txt

@AdrianKoshka commented on GitHub (Oct 17, 2018): I'm no CMake expert, but I see no reference to `libssh` here. https://github.com/debauchee/barrier/blob/master/CMakeLists.txt

gitea-mirror commented

2026-05-05 05:20:00 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Oct 17, 2018):

I would hazard a guess that some other library/dependency was updated on your system, and that is the culprit.

@AdrianKoshka commented on GitHub (Oct 17, 2018): I would hazard a guess that some other library/dependency was updated on your system, and that is the culprit.

gitea-mirror commented

2026-05-05 05:20:04 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 17, 2018):

I don't know... maybe the new version of libssh was messing something up. I have no idea. All I changed was the libssh package and now its ok... I didn't change any other package, and I even re-compiled barrier on all 3 pc's. Maybe its some other package that depends on libssh or something.

@johnny-mac commented on GitHub (Oct 17, 2018): I don't know... maybe the new version of libssh was messing something up. I have no idea. All I changed was the libssh package and now its ok... I didn't change any other package, and I even re-compiled barrier on all 3 pc's. Maybe its some other package that depends on libssh or something.

gitea-mirror commented

2026-05-05 05:20:07 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Oct 17, 2018):

Well, if you recompiled barrier, and other system libs were updated, that means barrier would've been compiled against the new libs, and would work.

@AdrianKoshka commented on GitHub (Oct 17, 2018): Well, if you recompiled barrier, and other system libs were updated, that means barrier would've been compiled against the new libs, and would work.

gitea-mirror commented

2026-05-05 05:20:11 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 17, 2018):

It didn't work until I changed libssh... its reproducable if I upgrade libssh.
sorry to have bothered you, I really like this project you've got here.

@johnny-mac commented on GitHub (Oct 17, 2018): It didn't work until I changed libssh... its reproducable if I upgrade libssh. sorry to have bothered you, I really like this project you've got here.

gitea-mirror commented

2026-05-05 05:20:13 -06:00

Author

Owner

@TafThorne commented on GitHub (Oct 18, 2018):

@johnny-mac do you have the /var/log/apt/history.log & term.log logs covering the upgrade that breaks the system and the downgrade that fixes it? That would show which packages changed.

@TafThorne commented on GitHub (Oct 18, 2018): @johnny-mac do you have the `/var/log/apt/history.log` & `term.log` logs covering the upgrade that breaks the system and the downgrade that fixes it? That would show which packages changed.

gitea-mirror commented

2026-05-05 05:20:15 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 18, 2018):

/var/log/apt/ ? I might have something like that for pacman. I did say one of my PCs is Devuan, but I don't think it was an upgrade in Devuan that caused this because there wasn't really anything updated on it.

@johnny-mac commented on GitHub (Oct 18, 2018): /var/log/apt/ ? I might have something like that for pacman. I did say one of my PCs is Devuan, but I don't think it was an upgrade in Devuan that caused this because there wasn't really anything updated on it.

gitea-mirror commented

2026-05-05 05:20:18 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 18, 2018):

Unfortunately I think I may have been wrong, I'm not really sure. To get barrier to work, I have to try to ssh to one of the client PCs, then barrier connects. Its odd. And I don't even have to type in the password, If I try to start a connection w one of them in ssh it just starts working. I really have no idea what to make of this.

@johnny-mac commented on GitHub (Oct 18, 2018): Unfortunately I think I may have been wrong, I'm not really sure. To get barrier to work, I have to try to ssh to one of the client PCs, then barrier connects. Its odd. And I don't even have to type in the password, If I try to start a connection w one of them in ssh it just starts working. I really have no idea what to make of this.

gitea-mirror commented

2026-05-05 05:20:19 -06:00

Author

Owner

@johnny-mac commented on GitHub (Oct 18, 2018):

Trying to ping one of the computers has the same effect as trying to SSH - the barrier connection fixes itself when I do that. Something must be broken under the hood, so I guess its probably not directly related to barrier, but to something somewhere else.

@johnny-mac commented on GitHub (Oct 18, 2018): Trying to ping one of the computers has the same effect as trying to SSH - the barrier connection fixes itself when I do that. Something must be broken under the hood, so I guess its probably not directly related to barrier, but to something somewhere else.

gitea-mirror commented

2026-05-05 05:20:21 -06:00

Author

Owner

@huyphams commented on GitHub (Oct 30, 2018):

I'm not sure if it can helps. I'm using libssh (in an other app) and it's broken after upgrading libssh to 0.8.3 (works fine with libssh < 0.8.3).

@huyphams commented on GitHub (Oct 30, 2018): I'm not sure if it can helps. I'm using libssh (in an other app) and it's broken after upgrading libssh to 0.8.3 (works fine with libssh < 0.8.3).

gitea-mirror commented

2026-05-05 05:20:23 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Aug 23, 2019):

Closing due to inactivity.

@AdrianKoshka commented on GitHub (Aug 23, 2019): Closing due to inactivity.

gitea-mirror commented

2026-05-05 05:20:26 -06:00

Author

Owner

@p12tic commented on GitHub (Aug 25, 2019):

Indeed, I don't see how libssh is related to Barrier. There's no dependency on libssh in barrier executables or the libraries they depend on.

@p12tic commented on GitHub (Aug 25, 2019): Indeed, I don't see how libssh is related to Barrier. There's no dependency on libssh in barrier executables or the libraries they depend on.

Rows
Columns

[GH-ISSUE #156] new version of libssh breaks barrier functionality #125