mosh-client and mosh-server link against libcrypto, so the ebuild should depend on dev-libs/openssl or dev-libs/libressl.
I've verified that mosh works with both libressl and openssl, but I haven't checked if it can be compiled when neither is present.
The bug has been closed via the following commit(s):
Author: Justin Lecher <email@example.com>
AuthorDate: 2019-01-02 10:50:16 +0000
Commit: Justin Lecher <firstname.lastname@example.org>
CommitDate: 2019-01-02 11:39:24 +0000
net-misc/mosh: Add missing dep
Package-Manager: Portage-2.3.53, Repoman-2.3.12
Signed-off-by: Justin Lecher <email@example.com>
net-misc/mosh/mosh-1.2.6.ebuild | 3 ++-
net-misc/mosh/mosh-1.3.0.ebuild | 3 ++-
net-misc/mosh/mosh-1.3.2.ebuild | 3 ++-
net-misc/mosh/mosh-9999.ebuild | 3 ++-
4 files changed, 8 insertions(+), 4 deletions(-)
Not fixed, but broken -- it's missing the libressl flag.
Come to think of it, the package shouldn't depend on either given how one or the other is always installed anyway.