Live data from Hacker News

Tl;dv: Over 180k meetings left wide open

bobdahacker.com

31–40 of 231 posts

Re: Tl;dv: Over 180k meetings left wide open

#31
post #15

I understand the need to shame this platform, but why expose all their clients to this much risk? This disclosure here just named a whole bunch of clients. Why?

What's the alternative? Seriously. He's spent six months trying to get them to fix it. The risk is already there.

Re: Tl;dv: Over 180k meetings left wide open

#32

Earlier quoted context omitted.

Fortunately we have LLM's to not produce that crap... wait, those LLM's were trained on the existing crap and produce the same crap... oh no.

I doubt SOTA models nowadays are going to produce an implementation without any kind of authentication like here, and not tell you about it. And even if, a later "is this ready for release" will probably surface such obvious issues. I do not think LLMs are the problem here. Today, they are most likely more competent than whoever set this up.

Still the six month wait time when everything should be good? /s

Re: Tl;dv: Over 180k meetings left wide open

#33
post #25

Earlier quoted context omitted.

You need to read the article.

I read the entire article. Did you? There’s no reason in there to expose this company’s clients. Edit - Are you capable of answering my actual question or was that the best you could do?

Read the article again, then. Anyone that has could get the list with a trivial amount of work. Security through obscurity isn’t going to hide that client list.

And who knows? Maybe someone competent whose company is a client will see that list and say, “hey, boss, I was on HN today, and…”

Re: Tl;dv: Over 180k meetings left wide open

#34

This is bad. I run a company in this space (deepfake voice phishing), and one of the most common pushbacks we hear from buyers is: “Where are attackers going to get audio clips of our employees?” ... excluding senior leadership, which most companies already recognize as a risk. Another similar incident that happened recently was 4TB/40,000 contractors voice + government ID + selfie leaked .. https://oravys.com/blog/m…

> 4TB/40,000 contractors voice + government ID + selfie leaked Leaked selfies? Do you mean ID photos?

Selfies are used during live ID verification. (All of this is supposed to be encrypted, and destroyed within certain regulatory bounds.)

Re: Tl;dv: Over 180k meetings left wide open

#37
post #25

Earlier quoted context omitted.

I read the entire article. Did you? There’s no reason in there to expose this company’s clients. Edit - Are you capable of answering my actual question or was that the best you could do?

He has been emailing the CEO for six months with no replies. This is has also been posted here before with not a single pip or comment ... :-) And these customers absolute lack of technical due diligence, on this nth example, of move fast and break things...makes them deserve what they are getting.

> And these customers absolute lack of technical due diligence, on this nth example, of move fast and break things...makes them deserve what they are getting.

That’s a garbage take. These customers didn’t move fast or break things. They trusted a company that made a promise and that company let them down.

Re: Tl;dv: Over 180k meetings left wide open

#38
I'm very intrigued by AI note takers, but I'm absolutely unwilling to expose me or my clients to this exact problem.

The solution (theoretically) is a purely local note taker, but I haven't found one that's any good. Tried meetily and others in the same vein, including briefly rolling my own. The breakdown in the pipeline seems to be reliable local diarization and speaker identification; even if the transcription is good, when speakers aren't accurately identified and speech isn't well grouped, there's no rescuing it in the summary step.

Re: Tl;dv: Over 180k meetings left wide open

#40

Earlier quoted context omitted.

Fortunately we have LLM's to not produce that crap... wait, those LLM's were trained on the existing crap and produce the same crap... oh no.

I doubt SOTA models nowadays are going to produce an implementation without any kind of authentication like here, and not tell you about it. And even if, a later "is this ready for release" will probably surface such obvious issues. I do not think LLMs are the problem here. Today, they are most likely more competent than whoever set this up.

However if you start current SOTA models out on a bad codebase they will happily write more bad code to fit in with the "conventions" of the existing code. Including authentication and isolation. If you start out your app on the wrong foot (for example because you lack the vocabulary to express what you need) you can end up with nicely polished turds

Asking the LLM for a review of the code would still have caught it

Post reply on HN