-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/10 04:06 , Sittampalam, Ganesh wrote:
While I agree with the potential benefits, I also worry that you will
end up making something that is far less well tested in practice. For
widely used and fairly low-level libraries like gnutls,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/11/10 04:41 , Brandon Moore wrote:
particular about cryptographic primitives. Some side channel attacks seem to
call for a very low-level language, to make it easier to verify that e.g.
execution time and the memory access pattern does not
Vincent Hanquez wrote:
On Fri, Oct 08, 2010 at 12:54:48PM +0100, Sittampalam, Ganesh wrote:
What's the motivation for this?
Well, I wanted to have a tls/ssl module that integrate nicely with
haskell.
until then the 2 solutions were:
- shelling out to curl: that's not great, usually
While I agree with the potential benefits, I also worry that you will
end up making something that is far less well tested in practice. For
widely used and fairly low-level libraries like gnutls, openssl and
zlib, I'm just skeptical that the benefits outweigh the risks and costs.
Anyway,
While I can see your point about potentially introducing new security holes,
and producing much less trusted code, I feel having tidy, pure libraries that
we can all integrate into our Haskell is a benefit that far outweighs this.
Especially when we have nice things like the type system,
On Mon, Oct 11, 2010 at 09:06:45AM +0100, Sittampalam, Ganesh wrote:
While I agree with the potential benefits, I also worry that you will
end up making something that is far less well tested in practice. For
widely used and fairly low-level libraries like gnutls, openssl and
zlib, I'm just
On Mon, Oct 11, 2010 at 09:41, Brandon Moore brandon_m_mo...@yahoo.com wrote:
While I can see your point about potentially introducing new security holes,
and producing much less trusted code, I feel having tidy, pure libraries
that we can all integrate into our Haskell is a benefit that far
On Fri, Oct 08, 2010 at 12:54:48PM +0100, Sittampalam, Ganesh wrote:
What's the motivation for this?
Well, I wanted to have a tls/ssl module that integrate nicely with haskell.
until then the 2 solutions were:
- shelling out to curl: that's not great, usually works until you have an
error, and
On Fri, Oct 08, 2010 at 02:08:29PM +0200, Christopher Done wrote:
Indeed. Easier to install, easier to hack on (for Haskellers). Haskell
program coverage, debugging, extending your quickcheck tests, etc.
absolutely.
I'm certainly hoping to quickcheck all that is quickcheckable. The next thing
Vincent Hanquez wrote:
On Fri, Oct 08, 2010 at 11:14:01AM +0530, C K Kashyap wrote:
Does native mean Haskell only - without FFI?
Native means the implementation is in haskell, and the library is not
using another implementation (in another language) to do the work:
either through FFI as a
On 8 October 2010 13:54, Sittampalam, Ganesh
ganesh.sittampa...@credit-suisse.com wrote:
Vincent Hanquez wrote:
On Fri, Oct 08, 2010 at 11:14:01AM +0530, C K Kashyap wrote:
Does native mean Haskell only - without FFI?
Native means the implementation is in haskell, and the library is not
11 matches
Mail list logo
