tty57 has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
djs55 has joined #mirage
tty57 has joined #mirage
nojb has quit [Ping timeout: 258 seconds]
tty57 has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
tty57 has joined #mirage
fmu has quit [*.net *.split]
tlockney_away has quit [*.net *.split]
mekaj has quit [*.net *.split]
tlockney_away has joined #mirage
tlockney_away is now known as tlockney
fmu has joined #mirage
mekaj has joined #mirage
nojb has joined #mirage
yomimono has joined #mirage
tty57 has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
tty57 has joined #mirage
yomimono has quit [Ping timeout: 272 seconds]
tty57 has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
tty57 has joined #mirage
brson has joined #mirage
avsm has joined #mirage
nojb has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
nojb has joined #mirage
nojb has quit [Quit: nojb]
nojb has joined #mirage
nojb has left #mirage [#mirage]
nojb has joined #mirage
nojb has quit [Client Quit]
nojb has joined #mirage
jimmyjones_thorn has joined #mirage
nojb has left #mirage [#mirage]
<jimmyjones_thorn>
Hey everyone, I've been trying out some Mirage skeletons and it looks very promising. I'm currently testing on Qubes, which works quite well. Has anyone considered tighter integration of Mirage + Qubes? It seems to me that this is a match made in heaven: disposable, stateless Mirage unikernels can narrow the attack surface of 'traditional' AppVM
<jimmyjones_thorn>
s and due to their small footprint, can be deployed extensively throughout the system.
nojb has joined #mirage
<avsm>
jimmyjones_thorn: yep, but noone's actively working on it. reports of success or failure most welcome on mirageos-devel@lists.xenproject.org
<jimmyjones_thorn>
I see.
<jimmyjones_thorn>
I have a few ideas for how these two projects can be integrated, but I don't have much time to work on it (as with everyone else, presumably).
nojb has left #mirage [#mirage]
nojb has joined #mirage
<jimmyjones_thorn>
If I get anything working 'manually' to prove the concept, though, I'll post to the list.
<avsm>
absolutely; would be met with interest, no matter how manual
<jimmyjones_thorn>
Cool, nice to hear. I'll play around with it for a few weeks at least, so don't expect anything groundbreaking tomorrow ;)
<jimmyjones_thorn>
Part of that is that I am new to OCaml (though I have done some minor stuff in SML a few years back and am familiar with FP), so if anyone has any good tutorial suggestions other than "Real World OCaml", I'm all ears.
<jimmyjones_thorn>
Actually, clicking that link brings up a major sticking point I see with integrating Mirage and Qubes--and more generally, just for any use of Mirage
<jimmyjones_thorn>
As far as I can tell, Mirage OS's security infrastructure is abysmal
<jimmyjones_thorn>
There are no signed packages, OPAM updates build your unikernel (gotta hope that hopelessly-broken TLS works!), and no clear statement of what components actually must be trusted
brson has quit [Quit: leaving]
brson has joined #mirage
brson has quit [Client Quit]
brson has joined #mirage
brson has quit [Client Quit]
<jimmyjones_thorn>
(and also, getting OCaml and OPAM set up on Fedora 20 was an adventure, though this is not Mirage's problem, per se)