| 13 Jun 2021 |
|  Boss joined the room. | 06:44:52 |
|  soapsudsxx joined the room. | 17:53:39 |
| 15 Jun 2021 |
|  tinystar joined the room. | 05:45:01 |
 numkem | I was wondering if what would be the proper way to manually parse a tzdata file in order to generate the .ets file for the tzdata library. I'm on nixos and I can't rely on the auto-downloader. | 14:49:14 |
| tinystar | Does anyone have a good setup for auto formatting .eex files? | 20:34:47 |
| 16 Jun 2021 |
 tcit | numkem: you may use https://github.com/mathieuprog/tz instead of tzdata | 06:10:01 |
|  alex0112 set a profile picture. | 16:46:19 |
| 17 Jun 2021 |
| numkem | In reply to @tcit:matrix.tcit.fr
numkem: you may use https://github.com/mathieuprog/tz instead of tzdata I tried it and it worked great! Thank you! | 01:29:48 |
| 22 Jun 2021 |
 MarqSven | Does anybody know how i can generate a public and private key in elixir? I know there is the erlang public_key app but i don't get it to work | 18:01:19 |
| MarqSven | I tried it with these arguments
:public_key.generate_key(ecParams: {:namedCurve,:prime256v1})
But that is not accepted
| 18:03:02 |
 croeso | it doesn't seem you need ecParams, but that is not a problem | 18:16:11 |
| croeso | If you look at public_key application there is only a number of curves supported | 18:16:56 |
| croeso | For instance x448 | 18:17:07 |
| croeso | all comes down to clauses of pubkey_cert_records:namedCurves | 18:18:03 |
| croeso | it might be that using ECParameters record could solve the issue, but I haven't tried | 18:25:17 |
| MarqSven | i found a package that abstract away this https://hex.pm/packages/ed25519 | 18:31:25 |
| MarqSven | With this i was able to solve my problem | 18:31:36 |
 uhoreg | Looks like I'm a bit late to the party, but I used erlang's crypto module. e.g. {pub, priv} = :crypto.generate_key(:eddsa, :ed25519) | 18:36:11 |
| uhoreg | * Looks like I'm a bit late to the party, but I used erlang's crypto module. e.g. {pub, priv} = :crypto.generate_key(:eddsa, :ed25519) | 18:36:37 |
| MarqSven | this would work without third party thanks, i will try that | 19:54:53 |
| MarqSven | The sign function should be :crypto.sign(:eddsa,:sha512,message,private_key)? | 20:14:09 |
| MarqSven | In reply to @hubert:uhoreg.ca
Looks like I'm a bit late to the party, but I used erlang's crypto module. e.g. {pub, priv} = :crypto.generate_key(:eddsa, :ed25519) * The sign function should be :crypto.sign(:eddsa,:sha512,message,private_key)? | 20:14:33 |
| MarqSven | because i get an argument error there. | 20:20:14 |
| uhoreg | I'm using :crypto.sign(:eddsa, :none, msg, [key, :ed25519]) and :crypto.verify(:eddsa, :none, msg, raw_sig, [key, :ed25519]) | 20:24:07 |
| MarqSven | thanks the last argument was missing the eddsa options | 20:25:56 |
| MarqSven | but in the docs http://erlang.org/doc/man/crypto.html#sign-4 these are optional | 20:26:25 |
| MarqSven | the Key argument | 20:26:45 |
| MarqSven | or is the | not the same as in elixir typedocs? | 20:27:08 |
| MarqSven | ah i see this is differnt from elixir. | 20:28:05 |
| uhoreg | Yeah, I seem to remember getting confused when reading those docs too. | 20:36:46 |
