@camfassett Welp! We discovered recently that they changed the PicoCTF mechanics this year. Last year, you were able to re-submit the same answer as someone else on the same team and the game would tell you whether or not the answer was correct. This made it possible to be on the same team but still solve problems (and thus try your hand at learning from them) individually. This year, the game doesn't permit this. Which I suppose makes sense if you're actually a physical classroom, but makes less sense for our situation. Sooo, weirdly, we…no longer really have a team.
You can still create an account as an individual (which you'd need to do anyways), though, so if you wanted to try your hand at the challenges, the best thing to do is simply register at https://2018.picoctf.com and then ping this channel when you're trying a puzzle. :)
Hey all lemme ask you something: what year is it?
Because I just spent the good part of a night and a bit of this morning trying to troubleshoot a problem with a USB boot disk thinking there was some bullshit about the filesystem I had to do some hardcore Matrix-fu on and you know what the actual solution was? The USB wasn't getting enough power. The solution, ultimately, was to unplug that shit and then literally wait 5 minutes and plug everything back in again. ???????????????????????????????????? Leaving me staring at the solution's success murmuring softly, "It's 2018" over and over again.
Anyway, for anyone who runs into this problem potentially, what happens is when you try to install an OS using a USB as your boot media, you might get this error that says
device descriptor read/64 error -110 -- that last number may vary. Essentially this is a sign that the USB isn't getting enough power to actually serve as a filesystem. After that, you get dropped into an emergency mode shell such as dracut.
To fix this:
I did not think this would work, but lo and behold, it fucking did.
Update for those who are enthralled with IRC: the above linked Digital Ocean guide turned out to be out of date enough that many things have changed. The newest release (alpha) of InspIRCd came out 5 days ago, also!
So, using the official InspIRCd wiki is proving to be much more fruitful thus far. Specifically, these installation instructions. I'm trying to get this set up now on a Debian stretch VM. Wish me luck, I'll reportback here. :)
I have been a little preoccupied as well, working on an Ansible role for Tor Onion services.
iptablesrole, which automates firewall configurations. Here's a somewhat complex example of auto-configuring the firewall based on a related role's configuration.
Unsure if anyone here can help but here's a problem I'm running into: I'm trying to have Prosody make s2s connections in a very small test network (two machines). I want userA@s1.invalid to be able to speak with userB@s2.invalid. Classic federation, nothing complex.
I can make this work when not using s2s TLS connections, but whenever I try to make s2s connections over TLS, I see a
policy-violation in Prosody's error log (when set to
debug), which says
Encrypted server-to-server communication is required but was not used. This message comes from this part of the code.
I can't quite figure out why this is happening, though, because I've already:
mcabber) in strict TLS mode (
set tls = 1) to verify that the mcabber client on s1.invalid can log in and authenticate as userB@s2.invalid from s1.invalid (ensuring that s1.invalid's root certificate store trusts s2.invalid's newly generated TLS certificate), and vice versa.
Sooo…I'm at a loss. It appears as though Prosody's s2s connections just aren't using TLS at all, even though I have explicitly required them and, AFAICT, set it up correctly so that it works flawlessly for at least c2s connections.
Here is a test branch of my current code in a Vagrant multi-machine environment that describes the above situation:
If you want to try it out, the Vagrantfile at that commit should be all you need:
vagrant up && vagrant provision --provision-with=tls
Thanks in advance.