Testing posting

Hello all,

The server fees are coming due shortly, and I'm not super happy with the setup, so I am going to take advantage of this timing and let the contract expire and re-tool the site, and re-launch it. I don't have a time frame, but in the mean time there is a decent group on Facebook (https://www.facebook...13075212286412/) and yes, I hate Facebook too, but it's not going away any time soon. I'd prefer to use Reddit, but it doesn't seem like anyone else seems to use it, so I'll leave it on Facebook. The contract runs out on the 16th, so on or around that time the site will stop working and I will redirect to the Facebook group temporarily. I hope to get the service manuals working again, as well as upgrade the site to the latest version of the software, as it's way behind in updates.

If you have any questions or concerns, please let me know.

Thanks

Tom

Hello all,

In case you are a techie and saw this mentioned on any news sites, redpepperracing.com *does* use Cloudflare, but does *NOT* use any of the affected services. I only use Cloudflare for DNS and nothing more. No information is cached using their service, so the bug does not impact our users privacy or any information leakage. If you have any questions or concerns, please let me know. You should also investigate this on your own, as many high profile sites were involved in the data leakage problem, so accounts on other sites may be compromised. Some useful links:

Cloudflare Report:

https://blog.cloudfl...are-parser-bug/

The researcher who found the bug:

https://bugs.chromiu.../detail?id=1139

https://github.com/p...aster/README.md

Blog about the bug:

https://www.engadget...pular-websites/

Another blog post:

http://gizmodo.com/e...ates-1792710616

A third blog post with some useful tips:

https://medium.com/@...d165#.namvgnpwj