Just a quick entry until I get the chance to do a full writeup – this is the tool I’m building. Basically a search engine that uses a popular social media website to get the most relevant fresh content. In conjunction with another API we gather and serve images all in an infinite scrolling gallery. This is all custom tailored through an intuitive user interface.
This project is still in development.
Source: http://mashable.com/2014/04/09/heartbleed-bug-websites-affected/?utm_cid=mash-com-fb-main-link
See my other post for more info on the Heartbleed Exploit.
| Was it affected? | Is there a patch? | Change your password? | What did they say? | |
|---|---|---|---|---|
| Unclear | Yes | Yes | “We added protections for Facebook’s implementation of OpenSSL before this issue was publicly disclosed. We haven’t detected any signs of suspicious account activity, but we encourage people to … set up a unique password.” | |
| Yes | Yes | Yes | “Our security teams worked quickly on a fix and we have no evidence of any accounts being harmed. But because this event impacted many services across the web, we recommend you update your password on Instagram and other sites, particularly if you use the same password on multiple sites.” | |
| No | No | No | “We didn’t use the offending implementation of OpenSSL in www.linkedin.com or www.slideshare.net. As a result, HeartBleed does not present a risk to these web properties.” | |
| Yes | Yes | Yes | “We fixed the issue on Pinterest.com, and didn’t find any evidence of mischief. To be extra careful, we e-mailed Pinners who may have been impacted, and encouraged them to change their passwords.” | |
| Tumblr | Yes | Yes | Yes | “We have no evidence of any breach and, like most networks, our team took immediate action to fix the issue.” |
| No | Yes | Unclear | Twitter wrote that OpenSSL “is widely used across the internet and at Twitter. We were able to determine that [our] servers were not affected by this vulnerability. We are continuing to monitor the situation.” While reiterating that they were unaffected, Twitter told Mashable that they did apply a patch. |
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| Apple | No | No | No | “iOS and OS X never incorporated the vulnerable software and key web-based services were not affected.” |
| Amazon | No | No | No | “Amazon.com is not affected.” |
| Yes | Yes | Yes* | “We have assessed the SSL vulnerability and applied patches to key Google services.” Search, Gmail, YouTube, Wallet, Play, Apps and App Engine were affected; Google Chrome and Chrome OS were not.
*Google said users do not need to change their passwords, but because of the previous vulnerability, better safe than sorry. |
|
| Microsoft | No | No | No | Microsoft services were not running OpenSSL, according to LastPass. |
| Yahoo | Yes | Yes | Yes | “As soon as we became aware of the issue, we began working to fix it… and we are working to implement the fix across the rest of our sites right now.” Yahoo Homepage, Yahoo Search, Yahoo Mail, Yahoo Finance, Yahoo Sports, Yahoo Food, Yahoo Tech, Flickr and Tumblr were patched. More patches to come, Yahoo says. |
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| AOL | No | No | No | AOL told Mashable it was not running the vulnerable version of the software. |
| Gmail | Yes | Yes | Yes* | “We have assessed the SSL vulnerability and applied patches to key Google services.”
*Google said users do not need to change their passwords, but because of the previous vulnerability, better safe than sorry. |
| Hotmail / Outlook | No | No | No | Microsoft services were not running OpenSSL, according to LastPass. |
| Yahoo Mail | Yes | Yes | Yes | “As soon as we became aware of the issue, we began working to fix it… and we are working to implement the fix across the rest of our sites right now.” |
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| Amazon | No | No | No | “Amazon.com is not affected.” |
| Amazon Web Services (for website operators) | Yes | Yes | Yes | Most services were unaffected or Amazon was already able to apply mitigations (see advisory note here). Elastic Load Balancing, Amazon EC2, Amazon Linux AMI, Red Hat Enterprise Linux, Ubuntu, AWS OpsWorks, AWS Elastic Beanstalk and Amazon CloudFront were patched. |
| eBay | No | No | No | “eBay.com was never vulnerable to this bug because we were never running a vulnerable version of OpenSSL.” |
| Etsy | Yes* | Yes | Yes | Etsy said that only a small part of its infrastructure was vulnerable, and they have patched it. |
| GoDaddy | Yes | Yes | Yes | “We’ve been updating GoDaddy services that use the affected OpenSSL version.” Full Statement |
| Groupon | No | No | No | “Groupon.com does not utilize a version of the OpenSSL library that is susceptible to the Heartbleed bug.” |
| Nordstrom | No | No | No | “Nordstrom websites do not use OpenSSL encryption.” |
| PayPal | No | No | No | “Your PayPal account details were not exposed in the past and remain secure.” Full Statement |
| Target | No | No | No | “[We] launched a comprehensive review of all external facing aspects of Target.com… and do not currently believe that any external-facing aspects of our sites are impacted by the OpenSSL vulnerability.” |
| Walmart | No | No | No | “We do not use that technology so we have not been impacted by this particular breach.” |
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| Flickr | Yes | Yes | Yes | “As soon as we became aware of the issue, we began working to fix it… and we are working to implement the fix across the rest of our sites right now.” |
| Hulu | No | No | No | No comment provided. |
| Minecraft | Yes | Yes | Yes | “We were forced to temporary suspend all of our services. … The exploit has been fixed. We can not guarantee that your information wasn’t compromised.” More Information |
| Netflix | Yes | Yes | Yes | “Like many companies, we took immediate action to assess the vulnerability and address it. We are not aware of any customer impact. It’s a good practice to change passwords from time to time, now would be a good time to think about doing so. “ |
| SoundCloud | Yes | Yes | Yes | SoundCloud emphasized that there were no indications of any foul play and that the company’s actions were simply precautionary. |
| YouTube | Yes | Yes | Yes* | “We have assessed the SSL vulnerability and applied patches to key Google services.”
*Google said users do not need to change their passwords, but because of the previous vulnerability, better safe than sorry. |
All the banks we contacted (see below) said they were unaffected by Heartbleed, but U.S. regulators have warned banks to patch their systems.
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| Bank of America | No | No | No | “A majority of our platforms do NOT use OpenSSL, and the ones that do, we have confirmed no vulnerabilities.” |
| Barclays | No | No | No | No comment provided. |
| Capital One | No | No | No | “Capital One uses a version of encryption that is not vulnerable to Heartbleed.” |
| Chase | No | No | No | “These sites don’t use the encryption software that is vulnerable to the Heartbleed bug.” |
| Citigroup | No | No | No | Citigroup does not use Open SSL in “customer-facing retail banking and credit card sites and mobile apps” |
| E*Trade | No | No | No | E*Trade is still investigating. |
| Fidelity | No | No | No | “We have multiple layers of security in place to protect our customer sites and services.” |
| PNC | No | No | No | “We have tested our online and mobile banking systems and confirmed that they are not vulnerable to the Heartbleed bug.” |
| Schwab | No | No | No | “Efforts to date have not detected this vulnerability on Schwab.com or any of our online channels.” |
| Scottrade | No | No | No | “Scottrade does not use the affected version of OpenSSL on any of our client-facing platforms.” |
| TD Ameritrade | No | No | No | TD Ameritrade “doesn’t use the versions of openSSL that were vulnerable.” |
| TD Bank | No | No | No | “We’re currently taking precautions and steps to protect customer data from this threat and have no reason to believe any customer data has been compromised in the past.” |
| T. Rowe Price | No | No | No | “The T. Rowe Price websites are not vulnerable to the “Heartbleed” SSL bug nor were they vulnerable in the past.” |
| U.S. Bank | No | No | No | “We do not use OpenSSL for customer-facing, Internet banking channels, so U.S. Bank customer data is NOT at risk.” |
| Vanguard | No | No | No | “We are not using, and have not used, the vulnerable version of OpenSSL.” |
| Wells Fargo | No | No | No | No reason provided. |
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| 1040.com | No | No | No | “We’re not vulnerable to the Heartbleed bug, as we do not use OpenSSL.” |
| FileYour Taxes.com | No | No | No | “We continuously patch our servers to keep them updated. However, the version we use was not affected by the issue, so no action was taken.” |
| H&R Block | No | No | No | “We are reviewing our systems and currently have found no risk to client data from this issue.” |
| Healthcare .gov | No | No | No | “Healthcare.gov consumer accounts are not affected by this vulnerability.” |
| Intuit (TurboTax) | No | No | No | Turbotax wrote that “engineers have verified TurboTax is not affected by Heartbleed.” The company has issued new certificates anyway, and said it’s not “proactively advising” users to change their passwords. |
| IRS | No | No | No | “The IRS continues to accept tax returns as normal … and systems continue operating and are not affected by this bug. We are not aware of any security vulnerabilities related to this situation.” |
| TaxACT | No | No | No | “Customers can update their passwords at any time, although we are not proactively advising them to do so at this time.” |
| USAA | Yes | Yes | Yes | USAA said that it has “already taken measures to help prevent a data breach and implemented a patch earlier this week.” |
WordPress
Unclear
Unclear
Unclear
WordPress tweeted that it has taken “immediate steps” and “addressed the Heartbleed OpenSSL exploit,” but it’s unclear if the issue is completely solder. When someone asked Matt Mullenweg, WordPress’ founding developer, when the site’s SSL certificates will be replaced and when users will be able to reset passwords, he simply answered: “soon.”
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| Box | Yes | Yes | Yes | “We’re currently working with our customers to proactively reset passwords and are also reissuing new SSL certificates for added protection.” |
| Dropbox | Yes | Yes | Yes | On Twitter: “We’ve patched all of our user-facing services & will continue to work to make sure your stuff is always safe.” |
| Evernote | No | No | No | “Evernote’s service, Evernote apps, and Evernote websites … all use non-OpenSSL implementations of SSL/TLS to encrypt network communications.” Full Statement |
| GitHub | Yes | Yes | Yes | GitHub said it has patched all its systems, deployed new SSL certificates and revoked old ones. GitHub is asking all users to change password, enable two-factor authentication and “revoke and recreate personal access and application tokens.” |
| IFTTT | Yes | Yes | Yes | IFTTT emailed all its users and logged them out, prompting them to change their password on the site. |
| OKCupid | Yes | Yes | Yes | “We, like most of the Internet, were stunned that such a serious bug has existed for so long and was so widespread.” |
| Spark Networks (JDate, Christian Mingle) | No | No | No | Sites do not use OpenSSL. |
| SpiderOak | Yes | Yes | No | Spideroak said it patched its servers, but the desktop client doesn’t use a vulnerable version of OpenSSL, so “customers do not need to take any special action.” |
| Wunderlist | Yes | Yes | Yes | “You’ll have to simply log back into Wunderlist. We also strongly recommend that you reset your password for Wunderlist.” Full Statement |
| Was it affected? | Is there a patch? | Do you need to change your password? | What did they say? | |
|---|---|---|---|---|
| 1Password | No | No | No | 1Password said in a blog post that its technology “is not built upon SSL/TLS in general, and not upon OpenSSL in particular.” So users don’t need to change their master password. |
| Dashlane | Yes | Yes | No | Dashlane said in a blog post users’ accounts were not impacted and the master password is safe as it is never transmitted. The site does use OpenSSL when syncing data with its servers but Dashlane said it has patched the bug, issued new SSL certificates and revoked previous ones. |
| LastPass | Yes | Yes | No | “Though LastPass employs OpenSSL, we have multiple layers of encryption to protect our users and never have access to those encryption keys.” Users don’t need to change their master passwords because they’re never sent to the server. But passwords for other sites stored in LastPass might need to be changed. |
update: The link in my article still works. Subtle Patterns has changed it’s format to a paid plugin, individual patterns are still available. Due to the pay to play nature of the photoshop plugin, they’ve removed links to the collection download.
I wanted to share a resource I’m completely infatuated with: Subtle Patterns. This website aggregates free to use subtle patterns, and shares user contributions to the rest of the community.
The best part of this website? They don’t make you jump through hoops to get their files! No sign-up, emails, or other crap no one really wants to deal with (why do you think my comments are registration free?). Even better, they have every pattern available for free, in a master pattern file. The default photoshop patterns suck (pardon me), and loading up this free subtle patterns download really gives you a great choice of patterns to integrate into your design work.
I had a user email me with some questions on installing subtle patterns into Photoshop. It’s really simple, just follow these steps:
Backup Link In case the github link goes down.
So I know many people see the RSS feed logo on a daily basis and have no idea what it does, or why it exists. RSS stands for rich site summary, and does exactly what the name implies – provides a detailed summary of what is happening with a blog, news feed, or website in general. Most people use RSS because it can streamline a user’s daily news. Instead of visiting all of the blogs I enjoy to check for new content, or signing up for newsletters, I can have news and posts piped right into my RSS client. In this case I’ll be using Mozilla’s discontinued Thunderbird mail and feed client. I love the program as a free offline mail program, for it’s scheduling ability, and feed following, did I mention it was free? Get it here.
This is an RSS icon, you’ve undoubtedly seen it before.
I needed to rename hundreds of files individually, with underscores instead of spaces. I could have named all of my files using spaces, and used str_replace among other PHP tricks to change them to underscores. Instead I turned to the powers that be (read: Google) and discovered a handy tool, AutoHotkey. This tool allows you to do anything from re-mapping a key, to completely automating tasks via it’s native scripting language and macros.
Direct from the AutoHotkey website:
AutoHotkey is a free, open-source utility for Windows. With it, you can:
- Automate almost anything by sending keystrokes and mouse clicks. You can write a mouse or keyboard macro by hand or use the macro recorder.
- Create hotkeys for keyboard, joystick, and mouse. Virtually any key, button, or combination can become a hotkey.
- Expand abbreviations as you type them. For example, typing “btw” can automatically produce “by the way”.
- Create custom data-entry forms, user interfaces, and menu bars. See GUI for details.
- Remap keys and buttons on your keyboard, joystick, and mouse.
- Respond to signals from hand-held remote controls via the WinLIRC client script.
- Run existing AutoIt v2 scripts and enhance them with new capabilities.
- Convert any script into an EXE file that can be run on computers that don’t have AutoHotkey installed.
This thing already saved me two hours of shift clicking by allowing me to remap my underscore to the spacebar. Totally a five-star piece of software and my open source recommendation of the month.