Linode hasn't been very forthcoming in the past where security "incidents" are concerned: http://arstechnica.com/business/2012/03/bitcoins-worth-22800... http://forum.linode.com/viewtopic.php?f=20&t=8509 I had really hoped that they had changed their stance on incident management. If it's true that they suppressed information about a possible wide-scale compromise where customer data could have been affected, then de…
Did you see http://www.linode.com/linode4.css and http://www.linode.com/linode3.css ? Nevermind the security concerns. These guys aren't using version control!
Linode hacked, CCs and passwords leaked
401–410 of 418 posts
Re: Linode hacked, CCs and passwords leaked
#402Earlier quoted context omitted.
That is one (good) way to handle the encryption. You don't want to leave out the compression or block size however, so add those back in. Most WAN links are low bandwidth enough that compression will not slow things down (this is usually true even on 1 GBE LAN links for pigz ) and in my experience the speed-up is substantial. pigz is much faster than using ssh compression as it is multicore. apt-get it or http://zlib…
the compression is unnecessary here, you're moving a max of less than a couple of hundred GB of data.
In most cases, compression at the raw block level will result in HUGE size savings, especially since a lot of that may be free space. It might even make this transfer tenable.
Re: Linode hacked, CCs and passwords leaked
#403I am an ex-customer of Linode and I'm still worried about this incident - Do they still store your card after you've quit the service? This is terrible :(
I've asked them this question. Here is the answer: Credit card information continues to be stored in our database in an encrypted format, and the decryption key is not stored electronically. We are working on a process on remove the credit card details of past customers on request and can handle this for you soon if you would like. If you have any further questions or concerns please let us know.
(It appears the answer is no, but given they haven't been forthright in the actual details of the hack, possibly not)
Re: Linode hacked, CCs and passwords leaked
#404Earlier quoted context omitted.
It depends on how sophisticated the identify theft is. I had a good friend who was taken for about $9000 in credit card fraud in 1998/1999, with Well Fargo. It took him the better part of six months, and endless correspondence with WF to prove all of the purchases were not his. There are lots of stories of people who were financially wiped out, to the point of bankruptcy, because of Credit Card/Identify fraud. With t…
That makes me wonder why the credit card system is so insecure in the first place. Why are credit card systems not secured with a password that the merchant never gets to see? Yet at the same time credit card suppliers keep bragging about how "secure" their cards are.
My bank in Sweden requires MasterCard SecureCode for all online transactions on their debit cards. Stores that don't support it simply won't work with the card.
So, it's up to the bank how secure they want it to be. The technology is there.
Re: Linode hacked, CCs and passwords leaked
#405Earlier quoted context omitted.
That makes me wonder why the credit card system is so insecure in the first place. Why are credit card systems not secured with a password that the merchant never gets to see? Yet at the same time credit card suppliers keep bragging about how "secure" their cards are.
> Why are credit card systems not secured with a password that the merchant never gets to see? My bank in Sweden requires MasterCard SecureCode for all online transactions on their debit cards. Stores that don't support it simply won't work with the card. So, it's up to the bank how secure they want it to be. The technology is there.
Re: Linode hacked, CCs and passwords leaked
#406Earlier quoted context omitted.
Bank of America provides this [1], as does Citibank [2] and likely others. Paypal at one time provided this service as well, but it doesn't seem to anymore [3] 1: https://www.bankofamerica.com/privacy/accounts-cards/shopsaf... 2: https://www.citibank.com/us/cards/gen-content/messages/van/i... 3: https://www.paypal.com/va/webapps/mpp/security/general-freet...
Nice. I wonder if any UK providers do this
Re: Linode hacked, CCs and passwords leaked
#407Earlier quoted context omitted.
I'd give another trust vote to Linode, anyway this could happen to anyone.
Linode really needs to make a statement about what happened with this hack, stating if credit card information was taken. A lack of communication does not help me trust them. I'd rather have them speak up as to what happened and know if I need to have my CC reissued.
Re: Linode hacked, CCs and passwords leaked
#408Earlier quoted context omitted.
> Why are credit card systems not secured with a password that the merchant never gets to see? My bank in Sweden requires MasterCard SecureCode for all online transactions on their debit cards. Stores that don't support it simply won't work with the card. So, it's up to the bank how secure they want it to be. The technology is there.
Of course, the main difference being signed up with such a bank makes is it's now harder to legally dispute fraudulent transactions on your card.
Re: Linode hacked, CCs and passwords leaked
#409Earlier quoted context omitted.
dd if=/dev/sda bs=1M | ssh root@ dd of=/dev/sda bs=1M let SSH handle compression for you instead.
That is one (good) way to handle the encryption. You don't want to leave out the compression or block size however, so add those back in. Most WAN links are low bandwidth enough that compression will not slow things down (this is usually true even on 1 GBE LAN links for pigz ) and in my experience the speed-up is substantial. pigz is much faster than using ssh compression as it is multicore. apt-get it or http://zlib…
Re: Linode hacked, CCs and passwords leaked
#410Earlier quoted context omitted.
Did you see http://www.linode.com/linode4.css and http://www.linode.com/linode3.css ? Nevermind the security concerns. These guys aren't using version control!
Renaming CSS files with numbers or whatever is one legitimate way to handle cache invalidation (not evidence of not using version control)