From: "Daniel Cegiełka" <daniel.cegielka@gmail.com>
To: musl@lists.openwall.com
Subject: Re: crypto visibility
Date: Thu, 15 Jan 2015 22:17:48 +0100 [thread overview]
Message-ID: <CAPLrYERGRRDa0bXf06EROFefQpXPYHaa429j-o2LU8S2aRrRtQ@mail.gmail.com> (raw)
In-Reply-To: <20150114222259.GM4574@brightrain.aerifal.cx>
2015-01-14 23:22 GMT+01:00 Rich Felker <dalias@libc.org>:
> On Wed, Jan 14, 2015 at 09:51:37AM +0100, Daniel Cegiełka wrote:
>> Hi,
>> Can we make these functions visible? They are very useful.
>>
>
> In short, no, at least not without a lot of other things happening. To
> do so would be to recreating one of the big things musl was designed
> to get away from: random nonstandard interfaces with no documented
> interface contract and behavior determined by whatever the existing
> implementation(s) happened to do. Note that making these interfaces
> public would also involve making the size and possibly representation
> of the state structure a public API/ABI too.
ok, I understand the reasons. Func's crypto API is totally different
per implementation and it is terrible, eg three times is added
SHA512's code to OpenSSH: crypt(), libc SHA512 and.. from
libressl/openssl.
btw. I have had some success in porting ssh code from OpenBSD CVS repo
to musl... but _without_ openssl :)
# file scp/scp sftp/sftp sftp-server/sftp-server ssh/ssh ssh-agent/ssh-agent s>
scp/scp: ELF 64-bit LSB executable, x86-64, version 1,
statically linked, stripped
sftp/sftp: ELF 64-bit LSB executable, x86-64, version 1,
statically linked, stripped
sftp-server/sftp-server: ELF 64-bit LSB executable, x86-64, version 1,
statically linked, stripped
ssh/ssh: ELF 64-bit LSB executable, x86-64, version 1,
statically linked, stripped
ssh-agent/ssh-agent: ELF 64-bit LSB executable, x86-64, version 1,
statically linked, stripped
ssh-keyscan/ssh-keyscan: ELF 64-bit LSB executable, x86-64, version 1,
statically linked, stripped
# ls -lh scp/scp sftp/sftp sftp-server/sftp-server ssh/ssh ssh-agent/ssh-agent>
-rwxr-xr-x 1 root root 89.8k Jan 14 19:07 scp/scp
-rwxr-xr-x 1 root root 131.2k Jan 14 19:07 sftp-server/sftp-server
-rwxr-xr-x 1 root root 146.7k Jan 14 19:07 sftp/sftp
-rwxr-xr-x 1 root root 336.9k Jan 14 19:07 ssh-agent/ssh-agent
-rwxr-xr-x 1 root root 482.1k Jan 14 19:07 ssh-keyscan/ssh-keyscan
-rwxr-xr-x 1 root root 616.8k Jan 14 19:07 ssh/ssh
tiring work... I think it is better to write ssh client for tinyssh
from scratch.
Daniel
> Rich
prev parent reply other threads:[~2015-01-15 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 8:51 Daniel Cegiełka
2015-01-14 17:58 ` Szabolcs Nagy
2015-01-14 22:22 ` Rich Felker
2015-01-15 21:17 ` Daniel Cegiełka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPLrYERGRRDa0bXf06EROFefQpXPYHaa429j-o2LU8S2aRrRtQ@mail.gmail.com \
--to=daniel.cegielka@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).