Edit: midiano.com is excellent! Super useful to be able to visualise MIDI's that way.
265 karma · joined February 1, 2016
Edit: midiano.com is excellent! Super useful to be able to visualise MIDI's that way.
In terms of the clicks and pops, if it's not an imposition, could you let me know if you hear similar artefacts in the Newgrounds game listed in the FAQ? That MOD file was specifically modified to try and minimise that issue and I'd be interested in if it sounds better or worse on your setup.
[edit] Here's a link to a reference sheet for Artsey.io, of which Ardux is a fork, it gives you a pretty good idea for how the board is used in practice: https://raw.githubusercontent.com/artseyio/artsey/main/layou...
Disclaimer: The visual artist is my wife ( http://montrose.is/sketching/about.html ) and the project has no attachment whatsoever to my dayjob.
And I should have been clear that a remapped root that drops drops privileges and/or transitions into another user is still better than an unremapped root doing the same. It's just that the remapping is not a panacea.
Almost no one has the resources to stand up to a targeted attack from even a mildly capable hacker. Therefore, the risk profile most administrators are working against are attacks of opportunity. In that race, as in the old joke about outrunning your friend instead of a lion, you need only be be some small amount more difficult to crack than the next potential victim.
There have been and will continue to be parts of the kernel hard-coded to respect UID 0. Until these are all found and fixed (likely many years from now) using usernamespaces to remap root will not provide all the safety one might assume. It is super handy for other users though.
Full disclosure - I am both a hatter and a sec guy.
Perhaps the article could have been clearer, but the advice is more subtle than it first appears. It ties into point 4 ("Don't use a single layer image"). You need to `yum update` at the right time to make good use of layering and to be able to control updates separately from builds.
Imagine you build both Nginx and Apache containers off the same distro image. Rather than having `RUN yum -y update && yum -y clean all` as the first step (which is easy to mess up or forget), you can instead build an "update" layer as a named image with it's own Dockerfile consisting solely of the `yum update`. Now your two application Dockerfiles can simply `from base-update-date`. This means you control when you get updates explicitly orthogonal to the application build and lets you run the two apps off slightly different versions, if there is indeed an issue you need time to resolve regarding backwards compatibility. This also means you get the most out of the caching mechanisms in Docker.
Full disclosure - I am both a hatter and a sec guy. [edit, spelling, grammar]
[1]: http://www.scirp.org/journal/PaperInformation.aspx?PaperID=7... "Cyclomatic Complexity and Lines of Code: Empirical Evidence of a Stable Linear Relationship"