unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: About Guile crypto support
Date: Wed, 06 Feb 2013 21:58:40 +0800	[thread overview]
Message-ID: <1360159120.2754.76.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CA+U71=N+rtrAZJzm0EJ4zXNsua22OOOw5ckt=0q11qFK8AF0Zg@mail.gmail.com>

hi Noah!

On Mon, 2013-02-04 at 21:57 -0500, Noah Lavine wrote:
> Hello,
> 
> 
> I was just thinking about this, and I was wondering, can you hash an
> arbitrary Guile object? And if so, what do you hash? (I mean,
> algorithms like SHA-1 are defined on sequences of bits, as I
> understand it. So what collection of bits do you hash?) And is the
> hash recursive? (I.e. is it an equal?-hash, an eqv?-hash, or an
> eq?-hash.)
> 
> 
> If I understand the conversation correctly, the answer is yes, and
> that you hash the bit representation that Guile uses internally, and
> it is an equal?-hash. Is that accurate?
> 
According to our talking about this topic, I'll explain something ;-P
My goal is not to hash arbitrary object. As I said, I'm dealing with
Server-design and web-framework, so what I need is to hash bytevectors
and strings. Since Guile2 uses character-string instead of byte-string,
I have to mention strings separately.
> 
Thanks!

> Thanks,
> Noah
> 
> 
> On Mon, Feb 4, 2013 at 9:43 PM, Nala Ginrut <nalaginrut@gmail.com>
> wrote:
>         On Tue, 2013-02-05 at 00:03 +0100, Ludovic Courtès wrote:
>         > Nala Ginrut <nalaginrut@gmail.com> skribis:
>         >
>         > > 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.
>         >
>         > We probably don’t want Guile to depend on libgcrypt.
>         >
>         
>         
>         No, I didn't mean to use libgcrypt directly, I just suggested
>         reuse part
>         of libgcrypt code(only the common digest algorithm) and make
>         wrapper,
>         then put the C code in libguile.
>         
>         > So, instead, I’d suggest choosing the best of the 10 gcrypt
>         FFI bindings
>         > already mentioned ;-), and putting it in the guildhall.
>         >
>         > If you want to go further, you (or its authors) could submit
>         it for
>         > inclusion in libgcrypt proper.
>         >
>         
>         
>         The gcrypt-guile project is doing so, I'll help it if I can.
>         But my original thought is orthogonal with gcrypt-guile, just
>         put some
>         common digest algorithm in libguile rather than a full-stack
>         crypto-lib.
>         
>         My suggest opposed by many guys, since they don't think
>         md5/sha are very
>         common things. ;-)
>         But I'm dealing with server & web framework development, so I
>         need
>         digest so much, and maybe it's no so common.
>         I'll let this topic alone, till others found they have same
>         requirements, or just forget about it. ;-D
>         
>         > Thanks,
>         > Ludo’.
>         >
>         >
>         
>         
>         
> 
> 





  reply	other threads:[~2013-02-06 13:58 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
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 [this message]
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=1360159120.2754.76.camel@Renee-desktop.suse \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=noah.b.lavine@gmail.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.
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).