News for hackers. Stuff that matters.
Re:Do not expose your RIGOL oscilloscopes to the internet by Mathnerd314 on Sunday July 16, 2023 @10:59AM (#36747715)
It looks like they never replied to him for months so he just published it. This would also fit with the HN title (conclusion in the post). I think if it was patched it would be "I found a bug".
Re:Do not expose your RIGOL oscilloscopes to the internet by pmontra on Sunday July 16, 2023 @11:37AM (#36748200)
From the timeline

> RIGOL says they would reply in 2-3 days, 1/28/23

> Full disclosure, 2/8/23

Those should be January 28 2023 and February 8 2023, which is the date of the post. It's only 13 days after the last communication from RIGOL, not months.

By the way, could at least us developers use ISO dates instead of whatever our local conventions are?

Re:Do not expose your RIGOL oscilloscopes to the internet by mlyle on Sunday July 16, 2023 @11:51AM (#36748361)
> It's only 13 days after the last communication from RIGOL, not months.

3 months of total stalling without a real reply to him. The last communication was only that they'd provide more details in a few days.

The fact that he asked again before the disclosure timeframe and they were like "uh, just give us a minute" doesn't change anything.

Re:Do not expose your RIGOL oscilloscopes to the internet by starlevel003 on Sunday July 16, 2023 @12:15PM (#36748601)
> By the way, could at least us developers use ISO dates instead of whatever our local conventions are?

2023-28 and 2023-39 aren't any more readable.

Re:Do not expose your RIGOL oscilloscopes to the internet by ooterness on Sunday July 16, 2023 @12:25PM (#36748701)
Usually when people say ISO8601, they mean "2023-07-12T09:20:00Z". But the actual spec, which no one reads because it costs money to access, allows dozens of other variations. (Too many IMHO.)

RFC3339 is compatible with "the good parts" of ISO8601 and it's also free.

https://www.rfc-editor.org/rfc/rfc3339

Re:Do not expose your RIGOL oscilloscopes to the internet by mulmen on Sunday July 16, 2023 @01:50PM (#36749715)
I interpret "ISO 8601" to be "lexicographically sortable in chronological order" or maybe "big endian".
Re:Do not expose your RIGOL oscilloscopes to the internet by jacquesm on Sunday July 16, 2023 @02:39PM (#36750153)
I prefer to use dd/mmm/yyyy with mmm like jan/feb/mar etc that takes care of all confusion and seems to be understood the world over. This saves me from having to adopt some local convention depending on who I'm invoicing.
Re:Do not expose your RIGOL oscilloscopes to the internet by mschuster91 on Sunday July 16, 2023 @06:06PM (#36751885)
Problem is you can't sort in that order.
Re:Do not expose your RIGOL oscilloscopes to the internet by jacquesm on Sunday July 16, 2023 @06:10PM (#36751917)
I don't think anybody reading my invoices will have trouble interpreting them, and if they need to sort then they're welcome to add their own version of the date. But at least there will be no ambiguity about when I sent the invoice.
Re:Do not expose your RIGOL oscilloscopes to the internet by kriive on Monday July 17, 2023 @11:16AM (#36759279)
Yeah, I agree that 13 days from the last contact was maybe a bit too fast. But they haven't replied to this day and I reported the vuln two months earlier without response!

P.S. sorry for the american time dates, I don't know what I was thinking lol.

Re:Do not expose your RIGOL oscilloscopes to the internet by SV_BubbleTime on Sunday July 16, 2023 @11:08AM (#36747836)
This sounds like Rigol and Siglent. Very impressive hardware for the price, questionable support and software.
Re:Do not expose your RIGOL oscilloscopes to the internet by nimish on Sunday July 16, 2023 @06:13PM (#36751941)
Siglent seems to be moving upmarket at least. Rigol has wildly good on paper hardware but their software is suspect.

Rigol made their own ADC chip that beats most off the shelf stuff yet they have some of the jankiest software and English translation known to man.