Announcement

Collapse
No announcement yet.

Apple Now Continuously Asking for Permission

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Any thoughts on implementing icloud app specific passwords instead of 2FA?

    I just setup my amazon alexa to use my icloud stuff with an app specific password and don't need to bother with the 2FA stuff.

    It's a requirement of apple to use 2FA to use App Specific passwords though.


    mike

    Comment


      #32
      Since App Specific passwords are basically just a complex password that you can use for ANY application which doesn't understand how to do 2FA I created one hoping that PHLocation would sign-in but alas no joy.

      [strike]So at this point I guess I'm stuck until a version of PHLocation with 2FA is released.[/strike] Darn, I really wanted to try this.

      Side Note: Would it be possible at some point to release PHLocation to the HomeSeer store as a free app? I only ask because adding or updating it on a ZEE S2 is a bit of a pain since one has to copy the files to a thumb drive then move them over to the ZEE S2. I can live with it as it is but it would be easier.
      Last edited by Timon; October 27, 2017, 11:24 AM.
      HomeSeer Version: HS3 Standard Edition 3.0.0.548
      Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
      Number of Devices: 484 | Number of Events: 776

      Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
      3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
      4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
      3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

      Z-Net version: 1.0.23 for Inclusion Nodes
      SmartStick+: 6.04 (ZDK 6.81.3) on Server

      Comment


        #33
        Found another thread that says 109 was updated to do 2FA so I tried this again.

        I'm on version 109 but I keep getting a login fail when logging into my iCloud account. I know I'm using the right username and password since I pasted the same one into my iCloud account but the logs says it's bad.

        I turn on level 2 debugging and I'm getting back:
        Oct-27 8:07:36 AM PHLocation
        (StartiCloud) Called.
        Oct-27 8:07:36 AM PHLocation
        (handleICL) from: 109 msg: (Authenticate) Called for: xxxxx@me.com
        Oct-27 8:07:37 AM PHLocation Error
        (handleICL) from: 109 msg: Prochttp EX: System.Net.WebException: Error: SecureChannelFailure (The authentication or decryption has failed.) ---> System.IO.IOException: The authentication or decryption has failed. ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: The authentication or decryption has failed. at Mono.Security.Protocol.Tls.RecordProtocol.EndReceiveRecord (System.IAsyncResult asyncResult) <0x72656590 + 0x000f4> in :0 at Mono.Security.Protocol.Tls.SslClientStream.SafeEndReceiveRec ord (System.IAsyncResult ar, System.Boolean ignoreEmpty) <0x726564a0 + 0x0002b> in :0 at Mono.Security.Protocol.Tls.SslClientStream.NegotiateAsyncWor ker (System.IAsyncResult result) <0x72653008 + 0x001b7> in :0 --- End of inner exception stack trace --- at Mono.Security.Protocol.Tls.SslClientStream.EndNegotiateHands hake (System.IAsyncResult result) <0x72657318 + 0x000b8> in :0 at Mono.Security.Protocol.Tls.SslStreamBase.AsyncHandshakeCallb ack (System.IAsyncResult asyncResult) <0x72657028 + 0x00093> in :0 --- End of inner exception stack trace --- at Mono.Security.Protocol.Tls.SslStreamBase.EndRead (System.IAsyncResult asyncResult) <0x726506b8 + 0x00134> in :0 at Mono.Net.Security.Private.LegacySslStream.EndAuthenticateAsC lient (System.IAsyncResult asyncResult) <0x72650608 + 0x00047> in :0 at Mono.Net.Security.Private.LegacySslStream.AuthenticateAsClie nt (System.String targetHost, System.Security.Cryptography.X509Certificates.X509Certificat eCollection clientCertificates, System.Security.Authentication.SslProtocols enabledSslProtocols, System.Boolean checkCertificateRevocation) <0x7264ab80 + 0x0006b> in :0 at Mono.Net.Security.MonoTlsStream.CreateStream (System.Byte[] buffer) <0x7264a168 + 0x00107> in :0 --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetRequestStream (System.IAsyncResult asyncResult) <0x72658298 + 0x000e8> in :0 at System.Net.HttpWebRequest.GetRequestStream () <0x7263d478 + 0x000e3> in :0 at i+d.e (System.String A_0, System.String A_1, System.String A_2, System.Boolean A_3) <0x726308b0 + 0x0029f> in :0
        Oct-27 8:07:37 AM PHLocation Error
        (handleICL) from: 109 msg: (Authenticate) Auth failed for : xxxxx@me.com Check iCloud user / password is correct.
        Oct-27 8:07:37 AM PHLocation Error
        (handleICL) from: 109 msg: (StartService) Auth failed for: xxxxx@me.com Service startup failed.
        Is there some reason this won't work on a ZEE S2?
        HomeSeer Version: HS3 Standard Edition 3.0.0.548
        Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
        Number of Devices: 484 | Number of Events: 776

        Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
        3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
        4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
        3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

        Z-Net version: 1.0.23 for Inclusion Nodes
        SmartStick+: 6.04 (ZDK 6.81.3) on Server

        Comment


          #34
          Originally posted by Timon View Post
          Found another thread that says 109 was updated to do 2FA so I tried this again.

          I'm on version 109 but I keep getting a login fail when logging into my iCloud account. I know I'm using the right username and password since I pasted the same one into my iCloud account but the logs says it's bad.

          I turn on level 2 debugging and I'm getting back:






          Is there some reason this won't work on a ZEE S2?
          I suspect the issue is that the version of mono on your Zee doesn't support TLS1.2 which Apple requires.

          You need at least mono version 4.8 for it to work.

          Paul..

          Comment


            #35
            Originally posted by sooty View Post
            I suspect the issue is that the version of mono on your Zee doesn't support TLS1.2 which Apple requires.

            You need at least mono version 4.8 for it to work.

            Paul..
            Just checked and it reported "Mono JIT compiler version 4.5.1"

            Does anyone know what if any issues there are in updating the ZEE S2 to either the 4.8 version or the latest 5.x version? Also, what the procedure is.

            Thanks
            HomeSeer Version: HS3 Standard Edition 3.0.0.548
            Linux version: Linux auto 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
            Number of Devices: 484 | Number of Events: 776

            Enabled Plug-Ins: 3.0.0.13: AirplaySpeak | 2.0.61.0: BLBackup
            3.0.0.70: EasyTrigger | 1.3.7006.42100: LiftMaster MyQ
            4.2.3.0: mcsMQTT | 3.0.0.53: PHLocation2 | 0.0.0.47: Pushover 3P
            3.0.0.16: RaspberryIO | 3.0.1.262: Z-Wave

            Z-Net version: 1.0.23 for Inclusion Nodes
            SmartStick+: 6.04 (ZDK 6.81.3) on Server

            Comment

            Working...
            X