<kensan>
mato: Not sure if that is the right fix. Alternatively one could declare the strings as constants and us strlen.
copy` has joined #mirage
gameredan has joined #mirage
mort___ has quit [Quit: Leaving.]
argent_smith has quit [Quit: Leaving.]
mort___ has joined #mirage
mort___ has quit [Quit: Leaving.]
<dudelson>
I got a tls cert from let's encrypt and I'm trying to use it in the static site example from mirage-skeleton instead of the default cert. I made privkey.pem -> server.key, chain.pem -> ca-roots.crt, and cert.pem server.pem
<dudelson>
the unikernel fails when I start it with "ERR [application] main: Unix.Unix_error(Unix.EACCES, "bind", "")"
<dudelson>
does anyone know what I'm doing wrong?
<lobo>
dudelson: just out of the blue. if it is using port 443, you'll have to start it as root or with sudo
mort___ has joined #mirage
argent_smith has joined #mirage
argent_smith has quit [Quit: Leaving.]
<dudelson>
lobo: why's that? It's been working fine for me without sudo so far.
<Drup>
443 is usually reserved, you need superuser rights to bind to it
<dstolfa>
Drup: In typical UNIX access control, yes. If you have a MAC policy that allows you to bind to privileged ports as a certain user or group, then you don't need to be superuser
<dstolfa>
FreeBSD's portacl lets you do something like that, I'm sure that Linux has something similar
<dstolfa>
dudelson: You might want to make sure that you weren't running on a machine that had a policy like that running
<dudelson>
I changed the port back to 4433 and it works like I was expecting. I forgot I had previously
<dudelson>
set the port to 443 to try deploying the unikernel
<dudelson>
but I didn't know that that port was privileged, thanks for clarifying!