본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Avatar for Username

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

이 쓰레드는 보존되었습니다. 만약 도움이 필요하시면 새로운 질문을 올려주세요.

OSX Server 5.1 IMAP Mail with Thunderbird. Certificate problem - can't connect from Win7

  • 1 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: Matt

user1332724
user1332724
more options

We are setting up a new Apple OS X Server 5.1 provide an IMAP for internal mail. We are hoping to use Thunderbird as the client. On MAC workstations and laptops when we setup the new email account we are offered the option to accept and trust the local self signed certificate. Once accepted the email accounts function correctly. However, when trying the same procedure on Win7 workstations we don't get the option to trust and cannot connect to the IMAP server. We tried importing the certificate from one of the MAC workstations, but the Win7 workstation does not trust it. Any suggestions?

Just for info - file sharing, DHCP and DNS are operating correctly.

We are setting up a new Apple OS X Server 5.1 provide an IMAP for internal mail. We are hoping to use Thunderbird as the client. On MAC workstations and laptops when we setup the new email account we are offered the option to accept and trust the local self signed certificate. Once accepted the email accounts function correctly. However, when trying the same procedure on Win7 workstations we don't get the option to trust and cannot connect to the IMAP server. We tried importing the certificate from one of the MAC workstations, but the Win7 workstation does not trust it. Any suggestions? Just for info - file sharing, DHCP and DNS are operating correctly.

모든 댓글 (1)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

My guess is SSL/TLS is not configured for the changes that occurred following logjam.

Ensure the server is functioning with TLS1.2 and that valid certificates of at least 2048bytes are used Everything before TLS1.2 is broken and should not be used. That includes SSL in it's entirety

Keys less than 2048 are also no longer long enough to provide anything like the encryption required.. Breaking them is now at the level of "trivial"