Recent submissions

Comment · 11 years ago
I don't know.. Google confirms they covered my area. I really don't look for house cleaning services, so maybe I just didn't get targeted for ads.
Comment · 11 years ago
When I hear about companies like this going under, I always think how odd it is that I've never previously heard about them.

Then I realize, that may have been part of the problem.

Comment · 11 years ago
Comment · 11 years ago
> So far as I know (this is sort of my profession), there's no federal "burglars tools" law regarding malware.

To be fair, many "burglars tools" laws require possession of the tools WITH INTENT to perform a criminal action. The intent piece is key. Merely possessing lock picks is usually fine. But sulking around masked in bushes outside an office building with a pickset, rope, and an empty duffel bag might get you in trouble.

A good list of Lockpick laws collected and indexed state-by-state at http://toool.us/laws.html. You see that in most jurisdictions intent is required.

While malware laws are still much less mature, I would hope that similarly there'd be an intent requirement. Possessing malware for purposes of reverse engineering to develop protections is obviously important, and clearly an activity we would want to remain lawful (and hopefully unlicensed/regulated).

Conspiracy is probably the easier route to a conviction.

Comment · 11 years ago
I feel like that's a reasonable timeframe from 'hmm, something is odd' to 'we're pretty sure we fully understand the impact, time to notify users.'

There's a balance between early notification and misstating the impact.

Comment · 11 years ago
In the comments, they indicate that they're in the process of sending out emails to users. Sending lots of emails takes some amount of time; hopefully those are arriving in inboxes now.

It's low key given the impacts as they understand them now, but seems reasonable unless there's more to it than it currently known. We'll see how things develop in the coming days - just being forthcoming days after it was detected and providing guidance on how to respond is commendable though.

Comment · 11 years ago
No, I don't think you did. I certainly haven't seen anything about the root cause. Let's hope it comes in time.
Comment · 11 years ago
This is one of the things that scares me. If an attacker had access to dump their credential digests, could they also have modified the site to silently log credentials upon entry?

From their statements so far, it doesn't seem that happened, but it seems likely that it could.

Comment · 11 years ago
> I just write down my passwords.

People may laugh, but for many people that's a huge step up. I've tried explaining password managers to family members, and I've failed. The usability just isn't there for many classes of user, and as noted elsewhere in this thread losing access to that database is catastrophic.

Getting them to use unique passwords per-site, even if those passwords are written down and stored in their desk drawer, can be an improvement.

I'm far less worried about someone breaking into my (grand)?parent's house and stealing their password diary then compromises their bank account than I am someone popping some random site and re-using the compromised password.

Now for enterprise credentials where the (physically) stored credential and the service to which it's applicable have a closer proximity there's a higher change of this kind of meatspace targeting. But then, the 'common local admin password across all domain-joined machines' problem persists too.

Comment · 11 years ago
"Answer unclear, ask again later"
Comment · 11 years ago
I would also appreciate more detail, but that shouldn't be their first priority.

They note that they discovered the breach on 'Friday' so I imagine they have an ongoing Incident Response right now. They may not have or be ready to share this information at this time, and that's fine. They might be working with law enforcement, further hardening systems, and continuing to confirm their findings to date to ensure they've mitigated the full impacts.

What's important now is conveying how users are impacted and what steps they should take to protect themselves; hopefully the rest comes in time.

Comment · 11 years ago
> Maybe there are people out there who will accept much more inconvenience in exchange for avoiding the risk associated with a cloud-based service. But, for me, the inconvenience is simply too much.

Sure, it's a balance everyone has to find for themselves. As you note earlier, a cloud password manager is better than shared passwords.

I'm certainly happy to accept a bit more inconvenience than most. I only do banking on one device, and one device only. I set up per-device passwords for things like Gmail (and MFA for my primary password), I authorize mobile apps via API keys, and try to avoid services that require I use my password on multiple devices in the first place.

For the most part, devices I use frequently can access things I use frequently without passwords. For web services (like HN) I simply don't need to log in and comment that badly if I'm on an unusual device.

> So the choice once more, for me, becomes cloud-based password manager or no password manager at all.

If those are you're options, you're probably right to go with the cloud option. For many people, even a physical notebook of single-service passwords would be an improvement.

> (Though if you've found a good option, that will allow me to easily sync across my home desktop, laptop, office pc, tablet, and smartphone, without using the cloud, I would absolutely love to hear about it! Maybe something Bluetooth based?)

Not really. It's largely the magic of cloud synching that I don't like. A lot of people run standalone password managers like Keepass or 1Password and store the database in some sort of file synchronization service like Dropbox. I guess that's workable, but it's still not something I'm going to be doing.

I simply don't want a single place where all my passwords are available that isn't hardware physically under my control.

Comment · 11 years ago
While LastPass seems to be responding well, I find their entire service exceeds my tolerance for risk.

If you don't use a password manager, you've got 99 problems, but a centralized store of your credentials for everything that's a huge target by virtue of having thousands of similarly centralized users ain't one.

Using a password manager (good idea) and then storing all your passwords on a 3rd party service of which you have no control seems inherently risky. Lastpass is a huge target, and while I believe they generally take reasonable security measures, for many the risk of compromise may be greater than an encrypted stand-alone password database. Use a password manager, please, but keep it offline and don't aggregate it with loads of other people's databases.

This is one area where I feel strongly that the conveniences of 'Cloud' are outweighed by the risks.

Comment · 11 years ago
Thanks!
Comment · 11 years ago
~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~

NCC Group

Atlanta. Austin. Chicago. New York. San Francisco. Seattle. Sunnyvale.

Application Security Consultant

Full-Time, work visa sponsorship available

~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~

Long-time Hacker News readers will be familiar with Matasano Security, and will expect to see us post in this thread. This month, there will not be a post from Matasano Security. Effective today, there will no longer be a Matasano Security. Instead, we're officially rebranding as NCC Group.

In late 2012, Matasano was acquired by NCC Group joining iSEC Partners and later Intrepidus Group. Since that time, we've been working together, cross staffing projects and benefiting from each other’s expertise. It's been a slow, steady process of increasing cohesion. We've reached the point where we need to assume a single identity, that of NCC Group.

Being a part of this process as it unfolds reminds me a bit of watching the Voltron cartoon series as a child in the '80s. The show featured pilots each commanding their own robot lions. Robot lions are fierce, powerful beings. But when they came together they'd form Voltron - a giant humanoid robot with the lions compromising each of it's parts. I like to think this is what's happening at NCC Group. What were previously separate companies each well accomplished in computer security are becoming a single even more formidable entity. "Form arms and body! And, I'll form the head!"

So, what does this have to do with hiring?

Growing a larger company requires a larger number of individuals. We still need candidates with the same skills as always; programming, reverse engineering, protocol analysis, web application building/breaking, adversarial thinking. We need people who understand technology and can identify flaws in how it's implemented. We need those who can look at a security weakness, and accurately gauge it's relative risk to the organization. And we need folks who can communicate that risk to multiple audiences, in varying levels of detail.

There's no better time than now to join us. Our integration effort has opened up opportunity within the company to focus on areas of specialization, advance skills, and take on ever more complex projects and challenges. If you've always wanted to be part of something new, but found yourself averse to the risk of early stage start ups, joining us now might be a way to do both. We're stable but we're evolving and changing, and our employees will shape what we become.

If you want to learn more about us check out our: Blog - https://www.nccgroup.trust/us/blog/ Cryptopals - http://cryptopals.com/ Microcorruption - http://microcorruption.com/

If you're ready to apply, contact us at: https://www.nccgroup.trust/us/careers/

Please, bear with us on the sites above. We've migrated a boatload of content, and it's likely there will be some website wrinkles. We'll iron them out as soon as we can (mostly we'll just keep breaking interesting software).

~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~'`^`'~-,._.,-~

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton