[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 543: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 127: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 127: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4773: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4775: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4776: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4777: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3887)
Home Racing World • View topic - Slot Car Corner Website NOT affected by Heartbleed Vulnerabi

Slot Car Corner Website NOT affected by Heartbleed Vulnerabi

Check here for new product updates and technical help.

Slot Car Corner Website NOT affected by Heartbleed Vulnerabi

Postby SlotCarCorner » Thu Apr 10, 2014 9:42 am

Our Slot Car Corner website and online store is hosted by an eCommerce provider called CoreCommerce. As you can imagine, many of the website owners who use CoreCommerce (including us) contacted them about the Heartbleed vulnerability. Per CoreCommerce:

"CoreCommerce is using a version of OpenSSL that is NOT affected. We use the OpenSSL 1.0.0 branch which is well documented as NOT affected according to heartbleed.com"

We have also verified this independently using a third-party tool that checks for heartbleed vulnerability (http://filippo.io/Heartbleed/)

We appreciate your business and support!

:)
User avatar
SlotCarCorner
SCC Mechanic
 
Posts: 736
Joined: Tue Sep 04, 2012 7:45 am

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby HomeRacingWorld » Thu Apr 10, 2014 9:59 am

Thanks for the info and taking the time to let people know.
User avatar
HomeRacingWorld
HRW Janitor
 
Posts: 15569
Joined: Wed Aug 08, 2012 2:05 pm
Location: HRW Skunkworks

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby ElSecundo » Thu Apr 10, 2014 10:19 am

Fantastic, thanks for checking into it, Steve. :)
ElSecundo
The Great One
 
Posts: 1372
Joined: Wed Aug 29, 2012 6:26 pm
Location: Sellersburg, IN

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby cgingras » Thu Apr 10, 2014 12:36 pm

Even if Slot Car Corner Canada uses a different e-commerce provider than Slot Car Corner, we also were unaffected by this vulnerability. All customer information has been and is still safe and secure.

Happy shopping in black and yellow! :text-thankyouyellow:
User avatar
cgingras
SCC Mechanic
 
Posts: 404
Joined: Thu Sep 06, 2012 3:20 pm
Location: Québec, QC, Canada

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby Ember » Thu Apr 10, 2014 4:07 pm

Good to hear. Let's go shopping...
User avatar
Ember
Downunder Diorama Queen
 
Posts: 2904
Joined: Wed Oct 24, 2012 11:57 pm
Location: South western corner of the south eastern bit of Downunder

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby Jesla » Thu Apr 10, 2014 4:13 pm

Hold on....This does not mean that the 300 million plus servers have been patched yet.
Unless you have a direct connection to their server you are still vulnerable. Be aware that
every hop your data makes between you and them are still not secure.
Last edited by Jesla on Thu Apr 10, 2014 4:16 pm, edited 1 time in total.
User avatar
Jesla
HRW SlotCar Veteran!
 
Posts: 892
Joined: Wed Sep 05, 2012 6:45 pm
Location: East TN

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby Jesla » Thu Apr 10, 2014 4:14 pm

Remember 2/3rds of all servers are affected any one of with your data may pass
through on it's way to it's destination. We are likely to get a percentage of repaired
servers for weeks to come.....it's still not safe....even electronically filed US tax
returns are affected as well. Canada shut their tax return servers down yesterday
so the same could happen here as well.
User avatar
Jesla
HRW SlotCar Veteran!
 
Posts: 892
Joined: Wed Sep 05, 2012 6:45 pm
Location: East TN

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby Ember » Thu Apr 10, 2014 5:24 pm

One can not function in a state of permanent paranoia.

Keep a constant watch on your accounts. Reconcile your bank statements properly. Query anything you see as an anomaly. And live your life!
User avatar
Ember
Downunder Diorama Queen
 
Posts: 2904
Joined: Wed Oct 24, 2012 11:57 pm
Location: South western corner of the south eastern bit of Downunder

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby SlotCarCorner » Thu Apr 10, 2014 5:45 pm

User avatar
SlotCarCorner
SCC Mechanic
 
Posts: 736
Joined: Tue Sep 04, 2012 7:45 am

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby Jesla » Thu Apr 10, 2014 6:16 pm

User avatar
Jesla
HRW SlotCar Veteran!
 
Posts: 892
Joined: Wed Sep 05, 2012 6:45 pm
Location: East TN

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby SlotCarCorner » Thu Apr 10, 2014 6:59 pm

That's not how OpenSSL encryption works. The encryption/decryption takes place at the "end points" - for example, a PC (browser) and a remote host server. Once the data is encrypted, intermediate servers cannot decrypt the data. The encrypted data is merely "passed along" in packets (think of envelopes) to it's ultimate destination where it gets decrypted. Heartbleed "potentially" lets a hacker fake the remote host server out by making believe it is the remote client. Hackers are not exploiting the intermediate servers - they are (potentially) exploiting the actual host server.

:)
User avatar
SlotCarCorner
SCC Mechanic
 
Posts: 736
Joined: Tue Sep 04, 2012 7:45 am

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby Jesla » Thu Apr 10, 2014 7:06 pm

I'm not going to argue, but you are taking on an awful lot of liability over something you really can't control.
Information about HBB should be treated as would your heath.....get a second or even third opinion.
Last edited by Jesla on Thu Apr 10, 2014 7:22 pm, edited 1 time in total.
User avatar
Jesla
HRW SlotCar Veteran!
 
Posts: 892
Joined: Wed Sep 05, 2012 6:45 pm
Location: East TN

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby SlotCarCorner » Thu Apr 10, 2014 7:18 pm

While we appreciate your concern, we want to reassure you and our Customers we are NOT taking Heartbleed lightly. We have proactively contacted our eCommerce provider and have been assured the servers our online store is hosted on are NOT susceptible to Heartbleed. Further, we have tested this independently using two (2) different tests specifically designed to detect Heartbleed (and will run additional tests as we become aware of them). We have also researched this with colleagues at work who provide cyber services to many of the U.S. Government agencies and Fortune 500 companies. Unless some new information about Heartbleed surfaces that indicates some previously unreported exposure, we are confident our website is not at risk.

:)
User avatar
SlotCarCorner
SCC Mechanic
 
Posts: 736
Joined: Tue Sep 04, 2012 7:45 am

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby ElSecundo » Thu Apr 10, 2014 8:21 pm

Endpoints are the most vulnerable areas, true. However, there are reports coming in about people going to other unpatched sites, where man-in-the-middle attacks are used to steal personal information from the originator's cookies. Things are far from safe out there right now, and financial transactions at a patched site can actually open you up to attacks at other sites. This isn't a passive thing -- hackers can use the access they gain for virtually unlimited mischief, and they can steal a lot of what they need from an unpatched site to find what they want on your own machine, including information that you sent to patched sites. In the cyber security world, it's essentially the equivalent of suddenly discovering that the army, navy, air force and marines had all been accidentally given leave at the same time, and the only way you can tell the servicemen to get back to base is to track them down on foot -- and nobody is keeping a master list of who has and hasn't returned to base.

This will improve on a daily basis as more and more servers and firewalls are patched. Basically, the sooner you resume online transactions, the more risk you take. Hell, even the FBI's website got hit.

It's being described by security experts as a catastrophe -- it ain't over when the flood waters have subsided in your house. Personally, I'm not expecting to do any web transactions for a month, and I normally do a lot of web transactions.

The long and short of it -- make no assumptions about your security. Call SlotCarCorner, they're nice guys. :)
ElSecundo
The Great One
 
Posts: 1372
Joined: Wed Aug 29, 2012 6:26 pm
Location: Sellersburg, IN

Re: Slot Car Corner Website NOT affected by Heartbleed Vulne

Postby SlotCarCorner » Fri Apr 11, 2014 3:06 am

We respect other's opinions such as Jesla's and Kurt's; however, our position remains unchanged. Our website host was never running a version of OpenSSL that was vulnerable to Heartbleed. Keep in mind your payment information is NOT stored on our website servers. If you are still concerned your account may have been compromised, you can also change your personal password as a further precaution.

As Kurt suggests, if you are still uncomfortable, please call us to place your order - we will gladly accept a check or money order.

:)
User avatar
SlotCarCorner
SCC Mechanic
 
Posts: 736
Joined: Tue Sep 04, 2012 7:45 am

Next

Return to Slot Car Corner News Center



Who is online

Users browsing this forum: No registered users and 43 guests