Displaying 20 results from an estimated 5000 matches similar to: "libssh"
2019 Mar 06
2
[PATCH nbdkit] Add ssh plugin using libssh.
This adds a simple plugin using libssh (not libssh2). The intended
use for this is with virt-v2v when sourcing guests from VMware over
SSH.
We've had several years of problems getting our libssh-based driver
into qemu. By putting it into nbdkit instead we can bypass that.
However this also lets us combine ssh access with filters, in
particular the recently written ‘rate’ filter.
Rich.
2006 May 09
1
xmalloc symbol in libssh
Hi list,
(Please Cc: me in your replies because I'm not subscribed to this list.)
While trying to build lukemftpd staticaly on FreeBSD, I got a link-time
error. Libssh.a indeed provides the "xmalloc" symbol (I suppose there
are more). I wonder if this is whether intentional or not. It is a
very common function name, and I think it would be worth renaming
it to something like
2013 Nov 02
3
[PATCH] curve25519-sha256@libssh.org key exchange proposal
It should be compatible with the original patch. However I think that the shared secret should be encoded as a string, too. What does libssh do?
> Am 02.11.2013 um 05:46 schrieb Damien Miller <djm at mindrot.org>:
>
>> On Fri, 1 Nov 2013, Markus Friedl wrote:
>>
>> Here are three versions (patch against openbsd cvs)
>>
>> 1) repace nacl w/libsodium,
2014 Apr 20
2
bad bignum encoding for curve25519-sha256@libssh.org
Hi,
So I screwed up when writing the support for the curve25519 KEX method
that doesn't depend on OpenSSL's BIGNUM type - a bug in my code left
leading zero bytes where they should have been skipped. The impact of
this is that OpenSSH 6.5 and 6.6 will fail during key exchange with a
peer that implements curve25519-sha256 at libssh.org properly about 0.2%
of the time (one in every 512ish
2019 Mar 06
2
Re: [PATCH nbdkit] Add ssh plugin using libssh.
On 3/6/19 9:40 AM, Richard W.M. Jones wrote:
> ---
> plugins/curl/nbdkit-curl-plugin.pod | 22 +-
> plugins/ssh/nbdkit-ssh-plugin.pod | 150 ++++++++
> configure.ac | 17 +
> plugins/ssh/ssh.c | 521 ++++++++++++++++++++++++++++
> README | 4 +
> TODO | 10 +-
>
2001 Oct 07
3
Using -lssh as shared library
Hello! This is my first post to this list... ;)
I'm not shure if someone will be interested in this topic.
For me, it has interest, as long as I maintain 100+ unix
(linux) servers with dialup access and every package update
cost some significant time to download, so package size is
somewhat important here.
I looked to openssh and realized that package consists of
several programs, all uses
2020 May 21
9
[Bug 3168] New: libssh.a(utf8.o): undefined reference to symbol 'strcasestr@@GLIBC_2.17'
https://bugzilla.mindrot.org/show_bug.cgi?id=3168
Bug ID: 3168
Summary: libssh.a(utf8.o): undefined reference to symbol
'strcasestr@@GLIBC_2.17'
Product: Portable OpenSSH
Version: 8.2p1
Hardware: ARM64
OS: Linux
Status: NEW
Severity: critical
Priority: P5
2007 Feb 16
1
SFTP Library : IPv6 Address
Dear Respected one,
Does the SFTP client/server, provided as the part of the libssh,
support IPv6 addresses ? I have downloaded the libssh and still
working on the seperation of sftp out of libssh.
If any body has information about SFTP supporting IPv6 addresses,
please inform me.
Thanks & Regards,
Deepak D
2010 Feb 22
2
ld: Unsatisfied symbol "options" in file ./libssh.a[hostfile.o]
Hi All,
I have want to add a option in ssh_config to co-work with ldap.But when I am compiling , i was encountered a
ld error, which says "cc -o ssh-keygen ssh-keygen.o -Wl,+nodefaultrpath -L. -Lopenbsd-compat/ -lssh -lopenbsd-compat -lz -lnsl -lxnet -lsec -lgssapi_krb5 -lkrb5 -lpthread
ld: Unsatisfied symbol "options" in file ./libssh.a[hostfile.o]
1 errors."
The following is
2014 Apr 18
2
[Bug 2232] New: curve25519-sha256@libssh.org Signature Failures When 'ssh' Used with Dropbear, libssh Servers
https://bugzilla.mindrot.org/show_bug.cgi?id=2232
Bug ID: 2232
Summary: curve25519-sha256 at libssh.org Signature Failures When
'ssh' Used with Dropbear, libssh Servers
Product: Portable OpenSSH
Version: 6.6p1
Hardware: All
OS: All
Status: NEW
Severity: major
2015 Jan 06
2
RE: Fwd: [Cryptography] Why aren’t we using SSH for everything?
Damien,
What is the best document to use for documentation on SFTP? In other words, if I want to build an SFTP client library based on libssh.a, is there documentation about the series of messages I need to send over the wire?
Thanks,
ScottN
-----Original Message-----
From: openssh-unix-dev [mailto:openssh-unix-dev-bounces+scott_n=xypro.com at mindrot.org] On Behalf Of Damien Miller
Sent:
2004 Feb 11
0
Makefile.in: progressmeter.o has moved to libssh
Since progressmeter.o has moved to libssh, we don't need to explicitly
link it into scp and sftp any longer.
Index: Makefile.in
===================================================================
RCS file: /cvs/openssh/Makefile.in,v
retrieving revision 1.255
diff -u -r1.255 Makefile.in
--- Makefile.in 10 Feb 2004 02:01:14 -0000 1.255
+++ Makefile.in 11 Feb 2004 17:10:40 -0000
@@ -137,8 +137,8
2001 Apr 07
2
ssh/scp lib
Does anyone know of a libssh package or tarball
or does it only come in a single package right now.
It would be really nice to see this protocol spread to
other progs other than ssh/scp itself(i.e kde browser,
zope,etc..).
Am I alone on this one and have to split it up myself
or am I stepping on toes for someone else who has
already done this?
[Icarus] Factor (aka Daniel Yount)
factorf2 at
2013 Nov 02
0
[PATCH] curve25519-sha256@libssh.org key exchange proposal
if I understand http://git.libssh.org/projects/libssh.git/commit/?id=4cb6afcbd43ab503d4c3d3054b96a1492605ea8d
correctly, then the shared secret is encoded as a bignum,
probably because the rest of the code assumes it's a bignum
(e.g. for key derivation, etc). however, the DH public keys
are always encoded as strings (both in my patches and
in the libssh.org code).
Am 02.11.2013 um 07:57
2001 Feb 10
2
SNAP 20010209 fails to compile sftp on Slackware
Yo All!
openssh-SNAP-20010209.tar.gz fails to compile on Slackware. Patch at
the end of this message.
Here is the error:
gcc -o sftp sftp.o sftp-client.o sftp-common.o sftp-int.o log-client.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -L/usr/local/ssl -lssh -lopenbsd-compat -lcrypt -lz -lnsl -lutil -lcrypto -lwrap
openbsd-compat//libopenbsd-compat.a(bsd-arc4random.o): In function
2014 Apr 18
3
[Bug 2233] New: curve25519-sha256@libssh.org Signature Failures When 'sshd' Used with Dropbear Clients
https://bugzilla.mindrot.org/show_bug.cgi?id=2233
Bug ID: 2233
Summary: curve25519-sha256 at libssh.org Signature Failures When
'sshd' Used with Dropbear Clients
Product: Portable OpenSSH
Version: 6.6p1
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5
2004 May 28
4
sftp Client for Windows XP
Folks,
Excuse my ignorance on the subject but I'm new to OpenSSH and have been
tasked to write a 'sftp' Client for a home-grown application that runs on a
Windows platform.
The answers to my questions is probably on the List Archives but I'm not
able to find it even after a few search attempts.
So here goes...
1. Is it possible to even write a custom 'sftp' client for
2019 Mar 06
1
Re: [PATCH nbdkit] Add ssh plugin using libssh.
On 3/6/19 10:05 AM, Richard W.M. Jones wrote:
> On Wed, Mar 06, 2019 at 09:59:33AM -0600, Eric Blake wrote:
>> On 3/6/19 9:40 AM, Richard W.M. Jones wrote:
>>> +Parts derived from Pino Toscano’s qemu libssh driver.
>>
>> Is that a compatible license? Or I guess another way of wording it -
>> what is the license of libssh itself? The resulting ssh plugin may
2019 Mar 06
0
Re: [PATCH nbdkit] Add ssh plugin using libssh.
On Wed, Mar 06, 2019 at 09:59:33AM -0600, Eric Blake wrote:
> On 3/6/19 9:40 AM, Richard W.M. Jones wrote:
> > ---
> > plugins/curl/nbdkit-curl-plugin.pod | 22 +-
> > plugins/ssh/nbdkit-ssh-plugin.pod | 150 ++++++++
> > configure.ac | 17 +
> > plugins/ssh/ssh.c | 521 ++++++++++++++++++++++++++++
> > README
2016 Jan 19
2
OpenSSH portability & buildsystem fixes
Hi,
I recently ported OpenSSH to my hobbyist operating system. The portable
release is very straightforward to work with, but it had a few minor
issues where it assumes the existence of things that might not be on a
POSIX 2008 system. This are the list of issues I encountered that I
believe makes sense to upstream.
* <sys/param.h> is included in many files and isn't a standard