New AUSCORS NTRIP broadcaster requires TLS certificate

Yes, I was wondering about this myself, is this a real threat, someone grabbing your NTRIP connection data??? Maybe this secure connection will be necessary for the future of driverless cars? Curious, puzzled.

Hi guys,

I think you shouldn’t face difficulties with the ntrip.data.gnss.ga.gov.au (port 2101) mount point. Still, the higher the level of security is, the better. We’ll implement TLS support for you to work with a more secured connection.

Ok right from lecia documents, the fear is both user registry data discovery the way its currently handled on many caster systems. Also spoofing correction streams to steer planes and ships.

So they are getting ahead of it before anyone has a chance to exploit it.

As an added bonus it makes a bunch of perfectly good gear obsolete. Emlid to the rescue as a intermediary device.

1 Like

There is a lot of legacy devices out there that are absolutely ready for retirement. A lot of units that only support GPS+GLO, requires GPS L2P legacy signals to operate.
There will always be something out that provides the last “push of death”. This seems like such an event.

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.

Hi guys,

Getting back with great news :tada: Starting from the new 29 Beta 1 firmware, Reach supports TLS connection with AUSCORS. Don’t hesitate to share your experience with us if you try it out!

8 Likes

Thanks for getting that done so quickly Kseniia. I’ve just tested it today and seems to work fine. I’ll be testing it in the field next week.

Thanks again.

1 Like

I just checked auscors port 443 and all good

1 Like

Hi guys,

Thanks for your feedback! :slight_smile:

I am not being able to view the list of Auscors mount points in 29 beta 1. I can see them in 28.4.

1 Like

@noel

Can confirm this issue - I can no longer view auscors mount points and have to enter manually.

Hi guys,

Thanks for the report! We’ll check it, and I’ll write you back.

Hi,

I’m here with an update: we reproduced this and will be working on a fix. I’ll keep you posted on the news!

If you read the page ports 443 for SSL or port 2101 for unencripted. No new account, budiness as usual.

Hi guys,

We’ve just released a new 29 Beta 2 firmware with a fix, so now AUSCORS mount points should be shown in the app. Please let me know if it works for you!

Seems to work for me. However I find that when using the unsecure version via port 2101, the mountpoints load but not in order of proximity to the receiver (RS2). Not a big deal I guess, but it seems to behave differently to port 443.

Hi Tim,

Thanks for noticing! Do you use ReachView 3 on Android or iOS? Can you share screenshots of what the mount point list looks like with these 2 ports?

I use both iOS and Android but I haven’t tested it on Android yet. Attached are the screenshots from iOS. Given that port 443 now works, I’ll just use that.


Hi Tim,

Thanks for the sceenshots! It looks like ReachView 3 doesn’t receive the distance info from the 2101 port. That’s why it can’t sort the mount points by the distance.

1 Like