[SOGo] BTS activities for Monday, May 13 2024

2024-05-13 Thread SOGo reporter
Title: BTS activities for Monday, May 13 2024





  
BTS Activities

  Home page: https://bugs.sogo.nu
  Project: SOGo
  For the period covering: Monday, May 13 2024

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5968
	2024-05-13 11:04:54
	updated (open)
	Backend General
	sogod segfaults
	
	  
	
5967
	2024-05-13 11:10:33
	assigned (open)
	Packaging (Debian)
	Build packages for Ubuntu 24.04 LTS
	
	  
	
  
  




Re: [SOGo] SOGo v5.10.0 integration with Windows Server 2016 based domain

2024-05-13 Thread Marco Moock
Am 13.05.2024 um 06:15:24 Uhr schrieb Roman:

> Do you mean 636 instead of 686?

Yes.

> Windows server uses 636 port for sure because when I do "telnet
> home.arpa 686" it's open. But if I use hostname =
> "ldapS://home.arpa:636" - I can't connect with SOGo web page to LDAP,
> no security logs in Windows during that operation. But without "S" -
> hostname = "ldap://home.arpa:389; - it works as intended.

Use a sniffer (wireshark) and check if it tries to use TLS directly on
port 636.


Re: [SOGo] SOGo v5.10.0 integration with Windows Server 2016 based domain

2024-05-13 Thread Roman
Hi,Do you mean 636 instead of 686?Windows server uses 636 port for sure because when I do "telnet home.arpa 686" it's open.But if I use hostname = "ldapS://home.arpa:636" - I can't connect with SOGo web page to LDAP, no security logs in Windows during that operation.But without "S" - hostname = "ldap://home.arpa:389" - it works as intended.Maybe I also need to add domain client certificate to SOGo in order to get secure access?  12.05.2024, 23:38, "Marco Moock (m...@dorfdsl.de)" :Am 12.05.2024 um 05:44:53 Uhr schrieb Roman:  I keep getting these errors: " TLS: can't connect: Error in the pull function.. ldap_err2string ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)"   Although if I run the same command without the "S" - ( ldapsearch -H ldap://home.arpa -D "us...@home.arpa" -w "Password" -b "DC=home,DC=arpa" -d1 ) everything works fine. But the port 636 is open (checked with telnet).Add the port to the configuration to make sure it uses 686.Use a sniffer to verify it uses 686.