David Tomaschik

Yeah, it might not be bad. I thought (and in my own testing, it appears correct) that `"https://*/*", "http://*/*"` just works, but I was wondering if there was an edge...

I just ran into this same (surprising) issue. What about passing (at least) `--nonet` to `xmllint` by default? It will at least prevent it from reaching out to remote servers...

@machinexa2 You can disable XML/XSLT parsing by customizing parsers for syntastic in your `vimrc`: ``` let g:syntastic_xml_checkers=[''] let g:syntastic_xslt_checkers=[''] ``` Though I disagree with @lcd047 about what the default should...

@huornlmj Curious how you've seen it denoted in other CTFs. I haven't seen many with difficulty personally. (Though the CTF I help run uses a "101" tag for introductory challenges.)

That's fair. Can you explain how JSON fields affect the import/export process? (At least in the context of this.) I tried to implement it completely as a plugin, but it...

Just a thought: should they be per-user on the host? So if you have an unprivileged sliver and then privesc, launch a 2nd sliver, it would be nice to not...

Ah, this appears on hosts where users are provided by a mechanism other than `/etc/passwd`, i.e., LDAP, and because when CGO is disabled, go falls back on directly parsing `/etc/passwd`.

I realize this is quite old news, but this occurs because of section ordering. It's possible that the `.mmcu` section appears between `.text` and `.data`, but simavr loads `.text` and...

This seems new. I'm pretty sure it's due to 58d9b4f, specifically because /api/categories reuses the fields from the Challenge entity here: https://github.com/google/ctfscoreboard/commit/58d9b4f969db85a6a11be8d894843eff0da499f3?diff=split#diff-dca05d1a74f56abe283172cf3ccf470dL553

At the moment, the prerequisite data is only exposed to the UI as a met/not met boolean, so we don't have the information to display this. Consequently, it'll require a...