[...] so far the only critical issue that's been found, and that was fixed in a new release 2 hours after it was reported. There is no such thing as bugfree software, but I do feel comfortable running all my instances publically. This is not advice -- like you said, please make your own calls ;-)

ah good, so it is nothing specific, just guesswork based on a very superficial first glance -- it seems they believe FTP and TFTP are enabled by default, which is absolutely not the case (for good reason!). They did have one good point, regarding the first CVE (the path traversal), which is [...]

I'm asking because I'm the author, and I do take security seriously -- so if someone finds something I've overlooked, I'd very much appreciate if they let me know :-)

I currently believe that exposing it directly to the internet is safe, so please give me a ping if you recall the details.

> the security is not good enough for exposing on the public internet

do you have any specifics in mind, or is it a general vibe/impression you got?

what did you have in mind? best there is right now is the grid-view, a.ocv.me/pub/demo/pic...

nice, happy to see copyparty actually runs on risc-v! only ever tried it in qemu since I don't have any riscv boards :>

that does mean you'll be relying on cloudflare, and they'll be able to eavesdrop on all your traffic (so that's hella iffy) but all the other alternatives are way more work... Maybe that's good enough to get started at least!

unfortunately we are no longer in the comfy good old days when machines automatically became accessible from the internet just by hooking them up; these days there's NAT and (even worse) CGNAT getting in the way.

the copyparty readme has the "at home" section which explains the easiest quickfix,

...tell you the IP-address of the machine you ran it on.

if you're not able to connect, then it could be due to a firewall on the server; I think Ubuntu uses ufw, so try this: sudo ufw allow 3923

however, if you want to connect from another machine across the internet, then things get complicated:

to save you from making the wrong google searches, the systemd part isn't relevant :>

if you want to connect from another machine in your LAN, then the server's IP should be all you need to know -- try ipaddress:3923 because copyparty listens on port 3923 by default.

the command "ip a" will...

aw man, you beat me to it! a pizza so delicious it deserves the double mention

bollebygd needs to own up to their chicken-curry-banana-pineapple-peanut pizza and name it accordingly, would immediately go straight to the upper left corner

[2/2] Some typos, and the phrasing of the phone part. What i MEANT to say was "a lot of the code <at an early stage>", not a lot in general!

as it grew, it was mostly laptop-coding, still combined with phone-on-bus. Sorry for the confusion! And again happy to hear you're finding it useful :>

ah, about that -- should copypaste this short explanation from elsewhere:

so I recorded that part of the video 3am just wanting to finally finish it and get it out, and didn't notice a few mistakes until after posting it -- [1/2]

happy to see it solving real problems 😁

thanks for checking it out! hope it doesn't give you too much trouble 😁

yo, top 5 any% for sure 💪

oh hey that's my software! ...good luck lol