News for hackers. Stuff that matters.
Re:TinyEMU, a RISC-V/i486 VM for Linux in the Browser by jstanley on Tuesday October 30, 2018 @07:16AM (#18335441)
Interestingly the VM seems to have internet access via a DigitalOcean instance:

> Access to Internet is possible inside the emulator. It uses the websocket VPN offered by Benjamin Burns (see his blog[0]). The bandwidth is capped to 40 kB/s and at most two connections are allowed per public IP address. Please don't abuse the service.

[0] http://www.benjamincburns.com/2013/11/10/jor1k-ethmac-suppor...

Re:TinyEMU, a RISC-V/i486 VM for Linux in the Browser by s-macke on Tuesday October 30, 2018 @11:50AM (#18337867)
Yes, the emulated computer emulates a network device. This sends the Ethernet frames via web sockets to the proxy server. On the proxy server, the frames are written to a TAP device. Then some firewall rules do the rest.
Re:TinyEMU, a RISC-V/i486 VM for Linux in the Browser by Immortalin on Tuesday October 30, 2018 @11:52AM (#18337893)
Why do you even need the additional layer of redirection when most (port 80 tcp) traffic can be done straight from the browser?
Re:TinyEMU, a RISC-V/i486 VM for Linux in the Browser by jstanley on Tuesday October 30, 2018 @12:32PM (#18338439)
Most port 80 TCP traffic can't be done straight from the browser. E.g. it won't let you write arbitrary headers.

Cross-domain requests won't work for the majority of sites.

And non-HTTP requests can't be done at all from the browser, it would be a pretty limited "network interface" if all it could do was call out to XMLHTTPRequest.

Re:TinyEMU, a RISC-V/i486 VM for Linux in the Browser by ossm1db on Friday November 09, 2018 @12:08AM (#18412459)
Run the websocket proxy yourself and get much better performance: https://github.com/benjamincburns/websockproxy

From the FAQ: "net_url sets the URL of the websocket VPN." I did this and it works great.