freenode/#lisp - IRC Chatlog

10:27:08 shrdlu68 phoe: Are you familiar with ironclad internals?

10:30:26 phoe shrdlu68: nope.

10:34:11 phoe I just peeked into it though and ironclad looks like well-structured, LET* heavy code.

10:35:55 phoe If you ever decide to try and add DH to ironclad, I'll owe you a pint of your favorite drink.

10:36:11 phoe Because that's what I will need to use sooner or later within the crypto of the application I'll be writing.

10:37:34 shrdlu68 Me too.

10:37:45 shrdlu68 elliptic-curve dh too.

10:38:14 phoe and a bit of googling reveals http://leetayres.com/lisp-crypto.html

10:38:27 phoe but I don't know how usable this is, and it has no tests.

10:40:00 shrdlu68 Yeah I saw that too. The "makes some unsafe assumptions" caveat is scary too.

10:41:04 phoe In case of crypto, it's fairly scary, yeah.

10:43:11 phoe shrdlu68: https://github.com/fjames86/frpc/blob/master/auth/des/des.lisp

10:43:16 phoe Is this of any help?

10:52:46 shrdlu68 Yes. Wow so many implementations all over the place.

10:53:57 shrdlu68 Okay, let me get to work porting it.

12:13:01 Shinmera Might be saner to make a CL+SSL replacement based on bearssl than trying to make a secure TLS implementation in pure lisp.

12:22:58 shrdlu68 Shinmera: I started the project to write a TLS fuzzer, so I needed to write a TLS implementation from scratch anyway because the availabl implementations are not so flexible as to allow one to extend or "specialize" their behavior with ease.

12:25:22 shrdlu68 I initially wrote it in C, but realized I'd errd, so I rewrote it in Lisp. CLOS + having a full CL interpreter in a fuzzer makes a big difference.

12:25:33 Shinmera shrdlu68: Fair enough

12:32:11 Shinmera Even if it isn't completely secure, it might be usable as a bootstrap approach for an SSL Quicklisp

12:32:31 Shinmera BearSSL bindings would still be nice to have though.

12:34:00 sjl ugh, I think something somewhere in one of my projects is enabling the fare-quasiquote readtable globally

12:34:10 sjl *one of my projects' dependencies

12:34:25 sjl so then other stuff gets loaded with that readtable enabled

12:34:51 sjl and then when quicklisp tries to load the FASLs in another project that doesn't depend on fare-quasiquote, it breaks

12:35:38 sjl so I have to blow away ~/.cache/common-lisp and sit while ironclad recompiles again

12:36:14 sjl or maybe the recompile restart could work

12:36:28 sjl but it's still annoying... I wonder what's the best way to track it down

12:36:46 sjl the problem is that the symptom doesn't show until long after the cause is over

14:29:39 swflint_away ** NICK swflint

14:49:36 imprfcto hei

14:49:43 imprfcto are macros the forte of lisp?

14:49:48 imprfcto can I see an example?

14:49:54 beach Hello imprfcto.

14:50:25 beach Macros, generic functions, reader macros, first-class packages, first-class symbols, first-class classes, etc, etc, etc.

14:52:42 imprfcto arguably one could create C macros as well

14:53:03 imprfcto and use plugins such as ultisnips and stuff like that

14:53:05 beach Common Lisp macros are very different from C macros.

14:53:21 imprfcto in which way?

14:53:40 beach They transform code in the form of an internal data structure, as opposed to transforming strings.

14:54:17 beach That internal data structure is known by all reasonably experienced Common Lisp programmers, and it is standardized.

14:55:35 jackdaniel C doesn't support macros, only its preprocessor. In Common Lisp they are first-class citizen (like functions)

14:56:03 jackdaniel so you have whole language at your disposal when you write a macro

14:56:43 JuanDaugherty text, string, lang manip generally i would say

14:57:09 JuanDaugherty but yeah the macro/reader system is key

14:58:28 JuanDaugherty and nothing comes close after you set some general criteria

14:58:52 JuanDaugherty like 'is a general purpose lang'

15:00:00 beach * suspects that imprfcto is here for some reason other than learning about Common Lisp and its unique features.

15:01:29 imprfcto beach: did you read my second line?

15:01:41 beach I did, yes.