I am looking for the FQDN of a SUPL server, version 2.0. I know that supl.google.com exists but it is for version 1.0.
Please post the name and port number of a SUPL 2.0 server and let me know if it requires TLS.
FYI - SUPL servers are used to provide assistance information for location requests.
Google SUPL server supports SUPL 2.0 specification.
But as per my recent experiments, it supports only RRLP protocol. It does not support LPP protocol.
It only supports set based position calculations only( MS based). It does not support set assisted position calculations( MS assisted).
Google has recently started supporting SUPL 2.0 using the same FQDN. Make sure the device is camped on a WCDMA or LTE network.
Related
I am trying to find out the security protocols supported by Microsoft Graph API and the Office 365 Management APIs.
I could see Office365 supports TLS1.0, TLS 1.1 and TLS1.2, but they are going to stop support for TLS 1.0 and 1.1, sooner.
Does the above statement holds true for the aforementioned APIs as well? Please help.
Microsoft has teams dedicated to infrastructure and security making those decisions (which security protocols to support and which ones to drop).
Even if the roll out of those changes might not be identical from one service to another, eventually those things align.
So yes, in the long run, Microsoft graph will most likely drop support for TLS 1.0 and 1.0. Especially since change notifications has dropped it support for outbound calls. I can't provide any time frame though.
I need to connect a WinCE6.0 device to a web based server using HTTPS.
The problem: WinCE6.0 uses WinInet v6 which supports SSL2, SSL3 and TSL1.0 None of which are supported in the current (2018) best practices due to their security flaws.
I doubt I can drop in a newer version of WinInet and expect it to run.
I had thoughts of porting CURL to WinCE.
I'm thinking this issue has already been addressed by the CE community, but I'm not seeing an available solution.
How can I get an old embedded device to securely connect to the WWW?
From GuruCE:
If you want to use TLS 1.1 and 1.2 on CE a suitable solution is to use mbedTLS library from ARM. It has a BSD-like license, so not too restrictive. Only one change to the makefiles is needed to get it to work on CE.
I was testing our equipment TCP performance using iperf3, WiFi, powerline and ethernet. Do I need use the same version in both client and server so that I won't see weird issue or performance drop?
Current I'm using
server: iperf 3.1.3
client: iperf 3.0.11
Thanks
For the most part you can use different versions of iperf3 between the client and server. Clearly they'll only be able to use features / functionality that the client and server have in common.
There were some old "beta" versions of iperf3 that weren't compatible with later versions, but everything since the official 3.0 release should interoperate with everything else. If not, I'd consider that a bug.
I inherited a Cast Iron appliance which reports that it is version 5.0.1.5 - several years old and off support.
This is mostly used to talk to Salesforce, who just sent us an email saying they are turning off SSL 3.0 in a few weeks. POODLE.
Can anybody tell me if this version of Cast Iron supports TLS and will continue to work when SFDC disables SSL 3.0? Or point me to something that tells me how to check this myself? I'm drawing a blank with Google..
Better upgrade fast.. this broke a client instance..
http://www-01.ibm.com/support/docview.wss?uid=swg21687945
To answer my own question: yes, old Cast Iron version 5.0.1 does support TLS 1.0.
Salesforce shut SSL 3.0 off this past weekend on all their sandbox instances and our CI integrations are still happy.
Castiron version below 6.1.0.12 do not support TLS. Once salesforce switched off ssl in sandboxes our orchs (all 150) of them would not connect to salesforce.
We are upgrading to version 7.
Using VBScript, want to talk to a HTTPS website but it fails with:
The client and server cannot
communicate, because they do not
possess a common algorithm
Found out this is because it needs to use SSL3. How can I tell it to use SSL v3?
Thanks
ServerXmlHTTP relies on WinHTTP, which supports SSLv3. See the WINHTTP_FLAG_SECURE_PROTOCOL_SSL3 in the documentation. What version of MSXML are you using? You may want to try using one of the later versions. See the documentation on ProgID information.