aeaa3

Does this means that you have the ability to

a) impersonate the identities of your users and b) decrypt the SSL traffic of your users

?

Why would the user be entitled to the commercial SAAS platform's custom modifications?

Because the platform provider didn't pay for the database's commercial license.

> The ability to set up your own clone instance its completely meaningless

Isn't that the whole point?

Yes, currently these are never deleted.

I will probably update it to delete accounts that have been inactive for a year or something.

A little more information:

So, it's called fakemail but there is a real SMTP server in there. Attachments should work fine. Getting the web app to create SMTP accounts was quite tricky, I'm sure there are better ways but I ended up implementing the unix crypt() algorithm in C#.

Server is holding up fine so far (there was a rate-limiting bug which brought the site down yesterday). Logs show 37K unique IPs have accessed it since yesterday, and it seems to be using about 1% of the CPU (it's on a free VM in the Oracle Cloud).

There is a whole API sitting behind the web page, including proper authentication, but the frontend is very much a MVP.

Very few actual emails have been sent to it, so I'd love it if people could actually send stuff. There are a bunch of websites that can be used to send test mails, e.g.

https://www.gmass.co/smtp-test

https://www.smtper.net/

https://smtpserver.com/smtptest

https://dnschecker.org/smtp-test-tool.php

Most people these days are using a service provider for SMTP in production, so it isn't really possible to keep your prod and test configs in sync.

I do agree about using testing everything real tools, which is why this (fakemail) uses OpenSMTPD as the mail server.

All the work is in configuring it (similar complexity to your postfix configuration by the looks of it), interfacing to it, and deploying it (currently using ansible but will probably dockerize it).

The fact that no emails can get through to a real recipient is a feature.

The idea is that, in a a test environment, we should not actually deliver the mails to the recipient, instead making them available on a web page (or through an API).

This is all open source by the way, and can be self-hosted. All the code is at https://github.com/aled/fakemail.

The 429 response is sent when rate-limiting (based on IP address).

Either something is wrong with my rate-limiting code or there are many people behind a single IP address.

Anyway the limits are increased now.

Do we know whether the machine on which this occurred had ECC memory?

Not sure why you defend this practice. No other hosting provider requires copies of their user's passports.

I am also unable use Hetzner, due to their overreaching security process.

Would it be possible to recreate the ULA logic in a modern FPGA? And if so, to use it as a direct replacement in an original Sinclair/Amstrad?

Is this for real? The store, which looks pretty amateurish, has no products for sale ("out of stock") and the prices are vastly too good to be true.

DDR3 memory for 40c per gigabyte? Cheapest I can see on Amazon is 5 times that. 256GB of memory (plus the board itself) for $280? Not possible.

Sorry, I don't believe it.

The tech looks impressive and interesting.

How will you guys make money? As a prospective user, what are the chances of being rethinkdb'd?

Hopefully with Ubuntu 64-bit on Raspberry Pi, ZFS should work.

Not sure how much I'd trust it yet, though.