<kentonv>
XgF: Hmm, it looks like seccomp, except less flexible... he of course attacks seccomp as "insane" without any good argument...
<XgF>
Yeah, though I'd argue the libc-specificness of seccomp-bpf is problematic
<kentonv>
what do you mean?
<kentonv>
what does seccomp-bpf have to do with libc?
<XgF>
e.g. the list of syscalls you want to enable for DNS resolution differs between glibc and musl
<XgF>
and obviously if glibc suddenly starts using the new foo3 syscall then you need to update your bpf filter
<kentonv>
how does tame() do any better?
<XgF>
In the OpenBSD case, tame(2) and libc are developed together
<XgF>
In the Linux case, you could have a tame(3) which used seccomp-bpf so the libc could use its' own knowledge
<kentonv>
but tame() is a syscall, right?
<XgF>
In OpenBSD, yes
<XgF>
But there is no reason it /has/ to be
<XgF>
A portable process sandboxing interface would be useful
<kentonv>
wait wait
<kentonv>
it doesn't help to implement it in libc, because the thing you are sandboxing may very well use a different libc
<kentonv>
certainly true in Sandstorm's case
<XgF>
That's very true in Sandstorm's case; not in many of the cases one wants to use seccomp-type-privdrops for
<XgF>
Personally my preferred solution to all of this would be to replace Linux with a proper cap-based kernel :P
<kentonv>
well sure. :)
dwrensha has quit [Remote host closed the connection]
spangattack has quit [Ping timeout: 264 seconds]
spangattack has joined #sandstorm
dwrensha has joined #sandstorm
dcb has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
dwrensha_ has joined #sandstorm
dwrensha has quit [Ping timeout: 256 seconds]
dwrensha_ is now known as dwrensha
dcb has joined #sandstorm
dcb has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
dcb has joined #sandstorm
bb010g has quit [Quit: Connection closed for inactivity]
dcb has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
dcb has joined #sandstorm
gopar has quit [Remote host closed the connection]
dcb has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
dcb has joined #sandstorm
dcb has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
ArcTanSusan has joined #sandstorm
larjona has joined #sandstorm
<larjona>
Hi everybody. I'm deeping my toe in sandstorm.io, congratulations for working on it. I'll try to selfhost an instance,and try to learn how to package simple apps. Wish me luck!
<larjona>
Now, first question: where is the "announcements mailing list"? (if any) The link in "Get involved" web page points to sandstorm.io (website homepage)
ArcTanSusan has quit [Quit: ArcTanSusan]
<dwrensha>
larjona: on https:sandstorm.io, there's a box for "Join our mailing list for updates", right under the "pre-order hosting" button.
<larjona>
thanks dwrensha!
<larjona>
Hi again. I've deployed my sandstorm instance at lacaja.larjona.net (not sure why the DNS is not resolving, but that's a different problem. I can access from my home network). I have enabled github authentication, signed in with my github account, and granted admin privileges to that account. Now, I've tried to install Etherpad, but it gets stuck at "Downloading 0%..." (nothing else happens). Where can I look for diagnosing the problem?
<dwrensha>
larjona: maybe check whether there's anything interesting in /opt/sandstorm/var/log/sandstorm.log
<larjona>
nothing interesting there, only old stuff. Maybe I need some configuration tweaking so it is more verbose?
<dwrensha>
larjona: does the same thing happen for any app that you try?
<dwrensha>
larjona: does it work to upload apps instead?
<larjona>
No "sockets" folder in my /opt/sandstorm/var/
<dwrensha>
it would be /opt/sandstorm/var/sandstorm/socket/
<larjona>
sorry, yes
<dwrensha>
what filesystem permissions do you observe in that directory, if it exists?
<larjona>
its permissions are root:root, instead of root:sandstorm
<larjona>
*ownership
<dwrensha>
that sounds like it could be a problem
<larjona>
Fixed ownership, problem persist. Will look at permissions
<dwrensha>
hm... it might be a bad idea to go around tweaking permissions/ownership on individual files
<dwrensha>
I suspect your whole sandstorm install is root:root
<larjona>
I have dirs with root:root, and other with root:sandstorm
<dwrensha>
do you remember what options you chose when you ran install.sh?
<dwrensha>
in particular, did you put in a non-default value for the Server User?
<dwrensha>
(My hypothesis is that you've hit a bug in the install script)
<larjona>
I don't remember very well. How can I start from scratch? Just removing /opt/sandstorm and running the script again?
<dwrensha>
sudo sandstorm stop
<dwrensha>
sudo rm -rf /opt/sandstorm
<larjona>
thanks
<larjona>
reinstalled, didn't ask for "Server user"
<dwrensha>
did you chose "full server install"?
<dwrensha>
what do the permissions/ownership look like now?
<larjona>
I chose full server install. Now it's working, I just installed Etherpad. Will look at permissions,but I think I know what happened
<dwrensha>
do tell!
<larjona>
ownership and permissions look the same as before. What I think I did differently in the first install and this one, is that in the first install I chose URL http://lacaja.larjona.net:6080 , and this time, since I already learned to setup the nginx proxy, I chose http://lacaja.larjona.net
<larjona>
or maybe the problem is that before, I setup the nginx proxy and restarted nginx, but forgot to restart sandstorm. Anyway, I cannot reproduce the problem, so it's clear that something I did wrong in my first install, and now it's fixed. Thanks!
<dwrensha>
the "forgot to restart sandstorm" thing sounds vaguely plausible as an explanation
<dwrensha>
but I'm still a bit confused how sandstorm got in that bad state
<dwrensha>
do you mind sharing the current contents of your /opt/sandstorm/sandstorm.conf?
<dwrensha>
and, in your working setup right now, there are things owned by root:root in /opt/sandstorm/var/sandstorm?
<larjona>
(sorry, I didn't make backup before removing the buggy one). But I suppose that I chose lacaja.larjona.net:6080 before, since I read about the nginx proxy after installing
<dwrensha>
larjona: if you're going through nginx, you can make the BIND_IP be 127.0.0.1, so that Sandstorm would only be exposed to the outside world through nginx
<larjona>
great, thanks!
<dwrensha>
jparyani: I just learned about "SKIP_UNITTESTS=true"
<dwrensha>
now I can run the tests without resetting my oauth config :)
larjona has quit [Ping timeout: 264 seconds]
skeek has joined #sandstorm
* paulproteus
waves.
aldeka has quit [Remote host closed the connection]
ocdtrekkie has quit [Remote host closed the connection]
<paulproteus>
I'm going through them and submitting docs/etc. changes to address things.
<larjona>
I think the problem with email is, if I understood correctly, that your mail provider has to allow you to send mail with the sandstorm domain as sender.
<paulproteus>
Yeah, that's what it seems. Perhaps you can add that to your list of GANDI outbound allowed domains? It's a subdomain of your GANDI domain so I imagine that should be possible.
<larjona>
If yes, I suppose Gandi does not allow that (my work mail server does not, for example)
<paulproteus>
But I'm honestly not fully sure why that's required. So I might read the source to learn more or wait until tomorrow and ask jparyani.
<larjona>
I don't know how to do that. I also wonder if GMail,for example, allows that (for the case of other users selfhosting)
<paulproteus>
But basically larjona I don't have advice for you yet; will hope to in a day or so.
<larjona>
No problem in my side, I've enabled github authentication and workarounded the problem.
dcb has joined #sandstorm
* paulproteus
waves, hi dcb
<dcb>
paulproteus: howdy
<paulproteus>
Are you already a Sandstorm user? Just curious about it? Let me know if there's anything I can do to help you, or any questions you have.
<paulproteus>
I guess the reason that it needs to be able to send emails from the Sandstorm install domain is that apps themselves can send email, and those come from randomstring@sandstormhost.example.com
<paulproteus>
re: apps to install not sorted: Yeah, it's sorted by a subjective metric that makes it easier to find what we believe are the good apps and harder to find everything in general.
<dcb>
paulproteus: I'm not a sandstorm user, but I have been using cap'n proto quite a bit. That's why I'm hanging out here
<paulproteus>
Ah, awesome.
<paulproteus>
There's lots of cap'n proto talk that happens here, as well as Sandstorm, so I hope you'll enjoy your stay.
<paulproteus>
Other than your email email sending not working fully, I think that addresses the feedback you have so far. Let me know if I missed something.
<larjona>
Fine, thanks!
<paulproteus>
Great (-:
mort___ has joined #sandstorm
larjona has quit [Quit: Konversation terminated!]
mort___ has left #sandstorm [#sandstorm]
dcb has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<paulproteus>
w/in 31
<paulproteus>
...
todayman has quit [Read error: Connection reset by peer]
todayman has joined #sandstorm
gopar has joined #sandstorm
<paulproteus>
Howdy gopar !
<paulproteus>
Have you had time to look into the packaging tutorial yet, btw? If not, that's fine, but thought I'd ask.
<gopar>
paulproteus, yo! Sorry, I've had a couple of programming job interviews and another one tomorrow.
<paulproteus>
np at all.
skeek has quit [Quit: WeeChat 0.4.2]
<gopar>
paulproteus, I'll ask miguel if he's been able to review the stuff. Also I rsvp for the south bay meetup :)
<paulproteus>
Good luck with them! I'm sure they'll go well.
dcb has joined #sandstorm
dcb has quit [Ping timeout: 256 seconds]
todayman has quit [Remote host closed the connection]