Cannot use YAM to get emails with AmiSSL 4.3 #27

jerseywurzel · 2019-02-23T19:49:38Z

Hi Jens,
Thanks for AMiSSL4.3.
Unfortunately, YAM latest nightly build as of 23.02.19 can no longer connect to the live server to download emails, though it can connect to the upload server. It was working fine with V4.2. I just tried to re-install 4.2 but it didnt work because traces of 4.3 were still recognised. Real Amiga OS3.9 A1200/060. I hope its not that the real miggy is too slow now.

The text was updated successfully, but these errors were encountered:

jens-maus · 2019-02-23T19:59:12Z

And what exactly is a "live server" and "upload server"?!?!

jerseywurzel · 2019-02-23T20:09:36Z

Sorry. Live is the Outlook/Hotmail server, I use the same smtp.Live server to send emails too.

Futaura · 2019-02-23T21:25:29Z

So, you are saying POP3 doesn't work, but SMTP does? What are the server names? And are there any error messages?

Futaura · 2019-02-23T23:32:42Z

Have been looking more closely at this and using the OpenSSL command to connect to pop3.live.com, the same TLSv1.2 cipher is used with both 4.2 and 4.3, so there shouldn't be a speed related issue. This is using the OS4 build, I should add, but it should be the same on OS3.

Try OpenSSL s_client -connect pop3.live.com:995 and see what it says. Unfortunately, it seems the m68k build doesn't work under emulation on OS4, so I can't test it.

You may need to use the OS3 OpenSSL command from 4.2 (the 4.3 one is crashing for me under emulation on OS4). This will work with the 4.3 libs too.

jerseywurzel · 2019-02-24T17:08:05Z

Hi Oliver, Yes, pop3 doesn't work but smpt does. Pop3.live.com (also tried office365.outlook.com) Smpt was smpt.live.com which worked, but I've set now set up office365.outlook.com which also works On 23 Feb 2019 9:25 pm, Oliver Roberts <notifications@github.com> wrote: So, you are saying POP3 doesn't work, but SMTP does? What are the server names? And are there any error messages? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#27 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYg7jYfeuU5bND0EfPTDRIlUvE5fyf05ks5vQbHJgaJpZM4bOICe>.

jerseywurzel · 2019-02-24T17:12:11Z

I typed what you suggested and got a whole paragraph. It starts with Connected (000000) and ends with Timout : 7200(sec) Verify returncode: 0 (ok) Extended master secret : yes I thank you for looking but I will be away for Adweek from tomorrow, so no rush. Thanks wurzel On 23 Feb 2019 11:32 pm, Oliver Roberts <notifications@github.com> wrote: Have been looking more closely at this and using the OpenSSL command to connect to pop3.live.com, the same TLSv1.2 cipher is used with both 4.2 and 4.3, so there shouldn't be a speed related issue. This is using the OS4 build, I should add, but it should be the same on OS3. Try OpenSSL s_client -connect pop3.live.com:995 and see what it says. Unfortunately, it seems the m68k build doesn't work under emulation on OS4, so I can't test it. You may need to use the OS3 OpenSSL command from 4.2 (the 4.3 one is crashing for me under emulation on OS4). This will work with the 4.3 libs too. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#27 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYg7janCmCG1NUsYQxtojs2RkGkjDMgxks5vQc-agaJpZM4bOICe>.

Futaura · 2019-02-24T18:26:34Z

Posting the entire output from the OpenSSL command would be helpful. It is frustrating that AmigaKit hijacked my broken A1200, as I have no way of testing the m68k AmiSSL natively. And the m68k emulation on OS4 breaks AmiSSL it seems, which obviously doesn't help.

jerseywurzel · 2019-02-24T20:13:25Z

Hi Oliver, Ok I saved the output to a file and have copied to my phone. Hopefully, it will be attached. On 24 Feb 2019 6:26 pm, Oliver Roberts <notifications@github.com> wrote: Posting the entire output from the OpenSSL command would be helpful. It is frustrating that AmigaKit hijacked my broken A1200, as I have no way of testing the m68k AmiSSL natively. And the m68k emulation on OS4 breaks AmiSSL it seems, which obviously doesn't help. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#27 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYg7jcVfbVgUrsJ3Hu5Een1gI_NG6Gqlks5vQtlbgaJpZM4bOICe>.

Futaura · 2019-02-24T20:29:18Z

@jerseywurzel Nope - I think you can only attach files via the full web interface.

jerseywurzel · 2019-02-24T20:37:22Z

Ok, hope it's attached now?
log.txt

jerseywurzel · 2019-02-24T20:47:40Z

Hi Oliver, I think I've done it now. On 24 Feb 2019 8:29 pm, Oliver Roberts <notifications@github.com> wrote: @jerseywurzel<https://github.com/jerseywurzel> Nope - I think you can only attach files via the full web interface. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#27 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYg7jeFtgleAJoBcqcRhZWXYRo0qacmTks5vQvYfgaJpZM4bOICe>.

Futaura · 2019-02-24T20:55:45Z

Yes, thanks. May need to get you to re-run it later with extra debug output on, but I've got a deja vu feeling so will check back through the archives.

Does the OpenSSL command from 4.3 work for you or does it crash? Output looks like it is the 4.2 command.

Futaura · 2019-02-24T21:11:26Z

Ok, I knew this felt familiar - see #11 - did you make any changes to get previous versions of AmiSSL v4 working with YAM? ECDH key exchange is a potential issue still. Maybe cipher priority changed since OpenSSL 1.1.0g and/or older faster ciphers were removed, which is causing ECDH to be chosen when it wasn't before.

jerseywurzel · 2019-02-24T21:41:08Z

Sorry, but I don't know the difference in the commands you mentioned. I just installed 4.3 in the same directory as 4.2. It said it was deleting old ciphers. Then I opened a she'll and typed the command as you showed. Thanks On 24 Feb 2019 8:55 pm, Oliver Roberts <notifications@github.com> wrote: Yes, thanks. May need to get you to re-run it later with extra debug output on, but I've got a deja vu feeling so will check back through the archives. Does the OpenSSL command from 4.3 work for you or does it crash? Output looks like it is the 4.2 command. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#27 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AYg7jbSxkNTpP7ENlay3H-_ZN4Z-a1bdks5vQvxRgaJpZM4bOICe>.

jerseywurzel · 2019-03-04T17:39:51Z

Hi Oliver,
Not sure if you saw a reply; Im sure I sent one but it doesnt show here.

Not sure how to tell what version OpenSSL command (Version OpenSSL?) it used or how to change from one version to another -could you let me know?

Futaura · 2019-03-04T18:19:48Z

@jerseywurzel Yes, "version OpenSSL". Although, I am 99% sure the latest OpenSSL command is broken on m68k somehow.

What is your DefaultSSLCiphers setting in your YAM .config file? Sounds like you may need to adjust this like you did previously.

jerseywurzel · 2019-03-04T21:57:33Z

@Futaura
Ok, I tried version openssl but it wasn't found. So I searched and found a few in C:, SSLROOT, and previous versions of animal from 3.6 onwards. I tidied it all up but version command still didn't work, although dopus does. I've tried various versions but none enable yam to download mail, although uploading does. I can't find a defaultcipher setting in Yam at all but I wouldn't have amended them.
Do you need me to manually install previous versions of openssl and run the test command at all?
Thanks

Futaura · 2019-03-04T22:15:43Z

The OpenSSL command should be in AmiSSL: on OS3, IIRC. Don't worry about testing this further though.

Regarding DefaultSSLCiphers I refer you to #11 (comment) :-) Just wondering if something changed in this respect when you updated YAM.

jerseywurzel · 2019-03-05T17:53:34Z

Ah, I think you're onto it. The DefaultSSLCipher was:
ECDHE-RSA-AES128-SHA.

After changing it as per the previous comment, it worked! Thank you so much.
It looks like the default ciphers were changed somehow?

jens-maus · 2019-03-05T18:18:42Z

Can you please state what exactly you entered now as the new DefaultSSLCipher setting?!?

jerseywurzel · 2019-03-05T19:01:09Z

@ jens-maus
Yes, I entered
DefaultSSLCiphers = AES256-SHA

Also, I am using the OPENSSL command from the Amissl 4.3 download, version 1.1.1a 20 Nov 18.

jerseywurzel · 2019-03-08T10:35:48Z

@jens-maus
I was doing some testing using the OPENSSL command. The version 1.1.1a did not work (causing an error and freezing the miggy), but version 1.1.0g (from amissl4.2) does work

Futaura · 2019-03-08T10:56:20Z

@jerseywurzel Thanks for confirming - I've opened a separate issue (#28) for that.

Regarding your DefaultSSLCiphers, as @jens-maus told you a long time ago, that isn't one of the most secure settings. I would recommend trying setting it to the default and adding ":!ECDH" to the end. This will disable all the ECDH(E) ciphers that are problematic on m68k and choose the best of the rest instead. You could also try "DEFAULT:!ECDH" or "ALL:!ECDH". That said, some of the other ciphers may be problematic on m68k too.

jerseywurzel · 2019-03-09T10:17:38Z

@Futaura Hi Oliver,

On 08/03/2019, you wrote: @jerseywurzel Thanks for confirming - I've opened a separate issue (#28) for that. Regarding your DefaultSSLCiphers, as @jens-maus told you a long time ago, that isn't one of the most secure settings. I would recommend trying setting it to the default and adding ":!ECDH" to the end. This will disable all the ECDH(E) ciphers that are problematic on m68k and choose the best of the rest instead. You could also try "DEFAULT:!ECDH" or "ALL:!ECDH". That said, some of the other ciphers may be problematic on m68k too.

I've tried different combinations of DefaultSSLCipher settings. I'm not sure if it's because I'm not typing it correctly or not, but all connections fail except with AES256-SHA I've tried entering: ECDHE-RSA-AES128-SHA ECDHE-RSA-AES128-SHA:!ECDH ECDHE-RSA-AES128-SHA :!ECDH DefaultSSLCiphers = DEFAULT:!ECDH I restarted YAM each time so it would load the new configuration but none connect. Anything else I can try? Thanks

Futaura · 2020-01-18T18:28:28Z

@jerseywurzel I wonder - are you running MuRedox? If not, please give it a try (assuming you are still using MMULib). I think it may help.

jerseywurzel · 2020-01-18T19:55:50Z

Hi Oliver,

On 18/01/2020, you wrote: @jerseywurzel I wonder - are you running MuRedox? If not, please give it a try - I think it may help.

No, never even heard of it but I'll look it up. Thanks. Bye for now, -- Russell A lot of money is tainted -Taint yours and taint mine. weather: Partly Cloudy : 7.00 C, 44.60 F Winds : East 10.36 MPH, 16.67 KPH, 9.00 Knots Jersey Airport (EGJJ), United Kingdom

- No longer crashes on 68020/030 without an FPU (#37) - Found and fixed fundamental flaw specific to 68060 only - Split release into two libraries (68020-40 and 68060) - Hopefully fixes #8 and #27 also

Futaura · 2020-02-15T16:08:21Z

@jerseywurzel It will be interesting to see if AmiSSL 4.4 has improved your YAM experience - IIRC, YAM is compiled for AmiSSL 4.2, so it will automatically use AmiSSL 4.4 instead once you've installed it. I'm hopeful it will resolve your issue due to a fundamental flaw being fixes specific to running on a 68060.

jerseywurzel · 2020-02-16T12:14:18Z

Hi Oliver,

On 15/02/2020, you wrote: @jerseywurzel It will be interesting to see if AmiSSL 4.4 has improved your YAM experience - IIRC, YAM is compiled for AmiSSL 4.2, so it will automatically use AmiSSL 4.4 instead once you've installed it. I'm hopeful it will resolve your issue due to a fundamental flaw being fixes specific to running on a 68060.

Yes, YAM is much faster now. I have even changed to Default Cipher to: ECDHE-RSA-AES256-SHA384 And it still flies along. Thank you. Bye for now, -- Russell

Futaura · 2020-02-16T12:32:00Z

Fixed in ff6c5f9

Futaura added the duplicate label Feb 8, 2020

Futaura added a commit that referenced this issue Feb 8, 2020

Big m68k update:

ff6c5f9

- No longer crashes on 68020/030 without an FPU (#37) - Found and fixed fundamental flaw specific to 68060 only - Split release into two libraries (68020-40 and 68060) - Hopefully fixes #8 and #27 also

Futaura self-assigned this Feb 16, 2020

Futaura added AmigaOS3 bug labels Feb 16, 2020

Futaura added this to the 4.4 milestone Feb 16, 2020

Futaura closed this as completed Feb 16, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot use YAM to get emails with AmiSSL 4.3 #27

Cannot use YAM to get emails with AmiSSL 4.3 #27

jerseywurzel commented Feb 23, 2019

jens-maus commented Feb 23, 2019

jerseywurzel commented Feb 23, 2019

Futaura commented Feb 23, 2019

Futaura commented Feb 23, 2019

jerseywurzel commented Feb 24, 2019 via email

jerseywurzel commented Feb 24, 2019 via email

Futaura commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019 via email

Futaura commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019 via email

Futaura commented Feb 24, 2019

Futaura commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019 via email

jerseywurzel commented Mar 4, 2019

Futaura commented Mar 4, 2019

jerseywurzel commented Mar 4, 2019 •

edited

Loading

Futaura commented Mar 4, 2019

jerseywurzel commented Mar 5, 2019

jens-maus commented Mar 5, 2019

jerseywurzel commented Mar 5, 2019

jerseywurzel commented Mar 8, 2019

Futaura commented Mar 8, 2019

jerseywurzel commented Mar 9, 2019 via email

Futaura commented Jan 18, 2020 •

edited

Loading

jerseywurzel commented Jan 18, 2020 via email

Futaura commented Feb 15, 2020

jerseywurzel commented Feb 16, 2020 via email

Futaura commented Feb 16, 2020

Cannot use YAM to get emails with AmiSSL 4.3 #27

Cannot use YAM to get emails with AmiSSL 4.3 #27

Comments

jerseywurzel commented Feb 23, 2019

jens-maus commented Feb 23, 2019

jerseywurzel commented Feb 23, 2019

Futaura commented Feb 23, 2019

Futaura commented Feb 23, 2019

jerseywurzel commented Feb 24, 2019 via email

jerseywurzel commented Feb 24, 2019 via email

Futaura commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019 via email

Futaura commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019 via email

Futaura commented Feb 24, 2019

Futaura commented Feb 24, 2019

jerseywurzel commented Feb 24, 2019 via email

jerseywurzel commented Mar 4, 2019

Futaura commented Mar 4, 2019

jerseywurzel commented Mar 4, 2019 • edited Loading

Futaura commented Mar 4, 2019

jerseywurzel commented Mar 5, 2019

jens-maus commented Mar 5, 2019

jerseywurzel commented Mar 5, 2019

jerseywurzel commented Mar 8, 2019

Futaura commented Mar 8, 2019

jerseywurzel commented Mar 9, 2019 via email

Futaura commented Jan 18, 2020 • edited Loading

jerseywurzel commented Jan 18, 2020 via email

Futaura commented Feb 15, 2020

jerseywurzel commented Feb 16, 2020 via email

Futaura commented Feb 16, 2020

jerseywurzel commented Mar 4, 2019 •

edited

Loading

Futaura commented Jan 18, 2020 •

edited

Loading