Changing LDAP/LDAPS port in find about certipy

[noraj]

In what scenario is the port changed from the standard ports?

Real DC on real client infra.

[BrunoTeixeira1996]

Certipy/certipy/lib/ldap.py

Lines 50 to 57 in 2780d53

	class LDAPConnection:
	def __init__(self, target: Target, scheme: str = "ldaps"):
	self.target = target
	self.scheme = scheme
	if self.scheme == "ldap":
	self.port = 389
	elif self.scheme == "ldaps":
	self.port = 636

[fgeek]

In what scenario is the port changed from the standard ports?

[BrunoTeixeira1996]

In what scenario is the port changed from the standard ports?

My use case is a hack the box machine. I've noticed that the ports being used are 3268 and 3269 . That could be a flag like what certipy already does in auth with -ldap-port

[fgeek]

In what scenario is the port changed from the standard ports?

My use case is a hack the box machine. I've noticed that the ports being used are 3268 and 3269 . That could be a flag like what certipy already does in auth with -ldap-port

Alright. I just wanted to ask as I have never seen different ports in the field (not saying that this won't happen).

[BrunoTeixeira1996]

In what scenario is the port changed from the standard ports?

My use case is a hack the box machine. I've noticed that the ports being used are 3268 and 3269 . That could be a flag like what certipy already does in auth with -ldap-port

Alright. I just wanted to ask as I have never seen different ports in the field (not saying that this won't happen).

Yes thats totaly fine and your question makes total sense 😁
So you think this should be something to consider?

[BrunoTeixeira1996]

@fgeek I've created #198 and tested here and it worked.
Maybe double check if has everything you want :)

[BrunoTeixeira1996]

@noraj yep that happened to me as well.
I am not sure why this simple fix is taking too long to be reviewed however you could use my fork instead in the mean time