ousado has quit [Read error: Connection reset by peer]
ousado has joined #mirage
dmj` has joined #mirage
olle has joined #mirage
Haudegen has joined #mirage
Ulrar has joined #mirage
<Ulrar>
Hey, quick question, do I need to do anything specific to get DNS resolution in mirageos ? When I try to do a Client.get (cohttp) I get a "name resolution failed: unknown endpoint type"
argent_smith has joined #mirage
argent_smith has quit [Quit: Leaving.]
<Ulrar>
Seems like the answer is yes, you do have to do something. I figured it out reading the http-fetch example
<Ulrar>
Now figuring out how to handle tls ..
mort___ has joined #mirage
mort___ has quit [Client Quit]
mort___ has joined #mirage
mort___ has left #mirage [#mirage]
argent_smith has joined #mirage
Haudegen has quit [Remote host closed the connection]
mort___ has joined #mirage
Haudegen has joined #mirage
mort___ has left #mirage [#mirage]
<mato>
Is there a catch-up today at 17:00? There's been no announcement so far and nothing on the Wiki page.
<mato>
17:00 CEST that is.
<hannes>
mato: yes, I'll post a mail now
<kit_ty_kate>
hi everyone, is there a parser that would take ssh private keys and would give a Nocrypto compatible type (e.g. Nocrypto.Rsa.priv) somewhere already ?
<kit_ty_kate>
reynir maybe ?
<mato>
kit_ty_kate: @haesbaert might have something like that...
<hannes>
background story is that I started to use mirage-fs in my newest project (caldav server), and I've some suggestions for improving the API.
<Drup>
yomimono: you should open a letterbox, people that feel their libraries are up to the challenge!
<kit_ty_kate>
hannes: thanks! Everything seem to be in x509.Encoding.Pem (it seems so anyway)
<hannes>
feel free to raise your opinion in the mirage-fs issue
Lortex has joined #mirage
<hannes>
and off to the next topic, Solo5 development mailing list pre-announcement (@mato)!
<yomimono>
as with all big and sensible API changes, I think we should do it and regret that we didn't a year ago
<hannes>
yomimono: thanks to the efforts to split up mirage-types into a zillion libraries, it's now easier to change one API, such as the FS, at a time :)
<hannes>
mato: would you mind to talk about your pre-announcement?
<mato>
Right, so some time ago I conducted an informal vote among the top-5 Solo5 contributors about what to do for an additional communication channel for open-ended Solo5 development discussions
<mato>
And the overwhelming preference was to set up a new mailing list
<mato>
This is now (thanks mainly to hannes) ready for use, and I'm pre-announcing it here, feel free to subscribe at solo5-subscribe@lists.h3q.com
<Kensan>
+1! (Lot of persistence on by Adam on OpenBSD!)
<hannes>
the OpenBSD stuff was mainly done by adam steen / theotheradam (who's based in australia and an OpenBSD contributor!)
<TImada>
hannes: I want to do ..., I'm now checking the new APIs on Solo5. Please wait a while!
<djwillia>
mato: ricardo and I are getting closer to the point where we will want to talk about the steps to move forward with the "seccomp backend" so hopefully we can start that discussion in another week or two
<hannes>
TImada: sure :)
<hannes>
djwillia: \o/
<mato>
That sounds great. My current priorities are a) mailing list setup b) test and merge openbsd support c) arm64 ci
<mato>
then I'd basically like to do the long-proposed renaming, write a bunch of docs and do a release ASAP
<mato>
So IMO things like netmap, seccomp, nikhil's shmstream-based net device will be best tackled after a release.
<djwillia>
sounds good!
<hannes>
mato: yes, I agree. otherwise there will never be a solo5 release (and the last one is from more than a year ago)
<mato>
djwillia: ricarkol: the sooner you guys subscribe to the list, the sooner i'll send out the announcement about the list :)
<djwillia>
just sent my confirm to the bot :)
<Kensan>
mato: Looking forward to a Solo5 release since that will mean it will come with Muen support :)
<mato>
hannes: indeed. so we stick to the things that are in-flight and almost ready, and do the rest after
<djwillia>
oh wow it has been a long time since a release if the Muen support isn't in there!
<mato>
OT: Anyone looked into the recent Oracle announcement of "GraalVM"? The "polyglot" language interop looks interesting, possibly also relevant to multi-language libOS scenarios.
<Drup>
mato: graal isn't really new
<Drup>
(iirc, they sort of force a common representation, since everything boils down to a common VM)
<yomimono>
slightly more on-topic: kit_ty_kate made a nice tool for checking whether packages are ready for ocaml 4.07, which is now in rc2
<mato>
Is it JVM-based? Was not clear to me from an initial skim of the announcements.
<thomasga>
but that would be a good idea once we have a better mirage-fs signature
<hannes>
well, on my/our part, we develpo against mirage-fs for persistent storage, and instead of using mirage-fs-mem, i'd appreciate one day to use a git repository :D
<thomasga>
Also I think it's a mistake to not have partial reads (with offset/lenght) in the Irmin API, that will probably appear at some point.
mort___ has quit [Ping timeout: 264 seconds]
djwillia has left #mirage ["ERC (IRC client for Emacs 25.3.1)"]
ricarkol has left #mirage [#mirage]
mort___ has joined #mirage
pagurus` has joined #mirage
pagurus has quit [Ping timeout: 240 seconds]
pagurus` has quit [Ping timeout: 240 seconds]
pagurus has joined #mirage
thomasga has quit [Quit: Leaving.]
mort___ has quit [Quit: Leaving.]
mort___ has joined #mirage
Haudegen has quit [Remote host closed the connection]
<reynir>
kit_ty_kate: there's a few different formats for ssh private keys
<kit_ty_kate>
reynir: I had RSA without password working using the x509 library
<reynir>
ok great :-)
Haudegen has joined #mirage
<kit_ty_kate>
with password seems a lot harder though but I think I will just avoid using passwords for now ^^"
argent_smith has quit [Quit: Leaving.]
<reynir>
Yea :/
<hannes>
kit_ty_kate, reynir: if you find a spec what crypto / standard is used by ssh keys with password encryption, please let me know... I've seen various in the X.509 setting (and still have the long-term plan to implement them, but providing 3DES isn't anything I consider to be useful), I'm esp. missing ASN.1 OIDs for aes ciphers...
<hannes>
thx thomasga for the links, I'll think more about it over the next days/weeks :)
<reynir>
I think there's even more than one format with password encryption
<reynir>
There's a newer format with more rounds or something in the key derivation
<reynir>
I looked into the formats a bit a while ago and decided it was too complex
<hannes>
reynir: i looked into pkcs8 and could only find 3des there :|
<hannes>
"too complex" does not apply to me ;)
<reynir>
heh
<hannes>
i mean i'm not afraid of complexity here, more about implement weak crypto... i feel better in the honest way: no encryption, than weak encryption (3DES, red13)