Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AppArmor profile #13

Merged
merged 1 commit into from Feb 17, 2013
Merged

AppArmor profile #13

merged 1 commit into from Feb 17, 2013

Conversation

ioerror
Copy link
Contributor

@ioerror ioerror commented Feb 17, 2013

I've created a small AppArmor profile that should be at least mildly protecting.

@agl
Copy link
Owner

agl commented Feb 17, 2013

I have no idea about AppArmor, but if it works for you then LGTM.

agl added a commit that referenced this pull request Feb 17, 2013
@agl agl merged commit 8df38f6 into agl:master Feb 17, 2013
@ioerror
Copy link
Contributor Author

ioerror commented Feb 18, 2013

Thanks!

What is the golang way to install this file at make install-like time into /etc/apparmor.d/usr.bin.xmpp-client I wonder?

@agl
Copy link
Owner

agl commented Feb 18, 2013

Go doesn't have a notion of make install. If there were any packages, then that would be the obvious place to express that. Otherwise, I guess one just writes an install.sh script?

@ioerror
Copy link
Contributor Author

ioerror commented Feb 20, 2013

That seems to be a weird thing about go - if you write a network daemon, how does it start? Surely golang's toolchain wants to be part of an actual OS? :(

@agl
Copy link
Owner

agl commented Feb 23, 2013

No language tries to solve that, right? Configuring daemon status varies hugely across OSes, even within Linux one has systemd, upstart, SysV init etc. I think that has to be distrib specific as non-Ubuntu generally doesn't include AppArmor.

@ioerror
Copy link
Contributor Author

ioerror commented Feb 24, 2013

Adam Langley:

No language tries to solve that, right? Configuring daemon status varies hugely across OSes, even within Linux one has systemd, upstart, SysV init etc. I think that has to be distrib specific as non-Ubuntu generally doesn't include AppArmor.

Oh sure, I mean that autoconf/automake generally have a way to put a
file in /etc/init.d/foo or /etc/foo/foo.conf - that is the part I think
that is missing. There seems to be a way to put things in $GOPATH/bin
but there doesn't seem to be a way to put such files into something like
$GOPATH/etc or other places on the system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants