From: Daniel Hartwig <mandyke@gmail.com>
To: guile-devel@gnu.org
Subject: Re: About Guile crypto support
Date: Mon, 4 Feb 2013 09:14:56 +0800 [thread overview]
Message-ID: <CAN3veRc5SKWWFpiCZrJcYCpZ9PG9q_=ZJWrAznGoxty90T_4OA@mail.gmail.com> (raw)
In-Reply-To: <1359896146.2754.19.camel@Renee-desktop.suse>
Hello
On 3 February 2013 20:55, Nala Ginrut <nalaginrut@gmail.com> wrote:
> As mentioned in another thread about digest algorithm support in Guile,
> my plan is use part of implementation of libgcrypt and make a wrapper,
> then put into libguile.
> But now I found weinholt's Scheme industria lib, which contains all
> mainstream crypto(not only digest) algorithm.
> http://weinholt.se/industria/manual/crypto.html#crypto
As mentioned on that page, there are some issues that apply to any
pure Scheme implementation:
> Beware that if you're using some of these libraries for sensitive
> data, let's say passwords, then there is probably no way to make
> sure a password is ever gone from memory. There is no guarantee that
> the passwords will not be swapped out to disk or transmitted by
> radio.
Libgcrypt provides a means to specify that some data should be stored
in secured memory, which will never be swapped to disk. Doing
something similar in Guile may be problematic, at least with a
Scheme-only implementation.
> So what's your opinion, guys?
> Would you prefer C implementation or Scheme way?
As gcrypt is mature, reimplementing it in either C or Scheme just for
Guile does not seem useful — on it's own. An FFI wrapper or extension
benefits from upstream security and maintenance efforts.
If you have a particular interest in learning about crypto. algorithms,
by all means port or write your own implementation using whichever
language. If you want it to have a Scheme interface, then Scheme
seems a logical choice to use.
If your goal is only to provide crypto. support to Guile programs,
then time is better spent providing a wrapper to the existing library.
Concerns about adding an external dependency do not hold much weight
next to the advantages of directly using the library; “don't repeat
yourself”, and all that.
Perhaps you are aware that there an extension for gcrypt under
development, with modules for the hash and randomize functions:
<https://gitorious.org/gcrypt-guile/>.
Regards
next prev parent reply other threads:[~2013-02-04 1:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 12:55 About Guile crypto support Nala Ginrut
2013-02-03 15:37 ` Thien-Thi Nguyen
2013-02-04 1:14 ` Daniel Hartwig [this message]
2013-02-04 3:12 ` Nala Ginrut
2013-02-04 3:35 ` Daniel Hartwig
2013-02-04 4:15 ` Nala Ginrut
2013-02-04 23:03 ` Ludovic Courtès
2013-02-05 2:43 ` Nala Ginrut
2013-02-05 2:57 ` Noah Lavine
2013-02-06 13:58 ` Nala Ginrut
2013-02-05 15:48 ` Ludovic Courtès
2013-02-06 4:18 ` Daniel Hartwig
2013-02-06 4:28 ` Daniel Hartwig
2013-02-08 16:21 ` Ludovic Courtès
2013-02-09 1:37 ` Daniel Hartwig
2013-02-09 15:12 ` Ludovic Courtès
2013-02-09 17:02 ` Andy Wingo
2013-02-09 17:50 ` Mark H Weaver
2013-02-09 20:44 ` Noah Lavine
2013-02-09 21:53 ` Ludovic Courtès
2013-02-11 8:20 ` Andy Wingo
2013-02-11 9:15 ` Thien-Thi Nguyen
2013-02-11 10:46 ` Mike Gran
2013-02-11 13:14 ` Ludovic Courtès
2013-02-11 9:51 ` Nala Ginrut
2013-02-11 15:23 ` Greg Troxel
2013-02-12 1:12 ` Daniel Hartwig
2013-02-12 4:20 ` Nala Ginrut
2013-02-12 5:21 ` Daniel Hartwig
2013-02-12 7:40 ` Dynamic FFI vs Static FFI (was Re: About Guile crypto support) Mark H Weaver
2013-02-12 13:52 ` Ludovic Courtès
2013-02-12 18:24 ` Mark H Weaver
2013-02-12 21:49 ` Ludovic Courtès
2013-02-14 7:21 ` William ML Leslie
2013-02-15 13:34 ` Nala Ginrut
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN3veRc5SKWWFpiCZrJcYCpZ9PG9q_=ZJWrAznGoxty90T_4OA@mail.gmail.com' \
--to=mandyke@gmail.com \
--cc=guile-devel@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).