- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
05-23-2023 11:16 PM
Just opening the git-bash prompt takes some second and almost ten seconds for the prompt to appear.
Looking for examples on how to rermidiate this as my current effort has resulted in no improvemt changes.
05-24-2023 02:28 AM
Hi @Anders Rasmussen
Did you tried the suggested workaround to add exclusion by publisher+name+children?
Please share more information.
Thanks,
Tamir
05-24-2023 04:28 AM
I believe I have done both yes, but it does not seem to have any effect (i did request setting on epm client before trying)
05-24-2023 09:55 PM
Hi @Anders Rasmussen,
Did you add exclusions to the “Pass The Hash attack” policy?
Alternatively, did you add it to global exclusions?
Thanks,
Tamir
05-24-2023 11:52 PM
I assume you mean PTH as I showed in picture nr two in my last comment?
Have tried adding the exclusions to all rules in the "Windows Credential Harvesting" to no avail.
I will try adding it to global exclusions.
05-25-2023 12:36 AM
Thanks @Anders Rasmussen please keep us posted!
05-25-2023 06:06 AM
Tried adding it to Global Exclusions but this did not have an effect.
Tried first with location set, but also with location not set
Still an ~8 second delay in getting the prompt to appear on both tries.
05-28-2023 01:49 AM
Hi @Anders Rasmussen ,
Can you please share what exactly you tried to exclude? Was it the Git-bash?
You can try excluding the code repository folders that git-bash writes to from policies.
Please note that this is not secure and is only for test purposes.
Thanks,
Tamir
06-05-2023 02:07 AM
Hi
I added the exclusion of the git-bash.exe to the TP policies and WCH
Issue occurs on just starting git bash console.
Console appears fast, but the login promt takes ~8 seconds to appear.
It does also appears a commands are slowed down, I'll will report results of this later today.
Regards Anders
06-06-2023 01:48 AM
Hi @Anders Rasmussen,
I can suggest adding exclusions by git signature - “Johannes Schindelin”.
Other than that, the best way to analyze the logs and understand the root cause will be in a new customer support case. Link: https://community.cyberark.com/s/Submit-a-Case
Thanks,
Tamir
06-06-2023 03:44 AM
Adding exclusion by signature only did not have any effect either.
Only thing that works is setting Privilege Threat Protection to Off!
06-07-2023 06:01 AM
Hi @Anders Rasmussen,
Please open a new customer support case so the team will be able to analyze the logs and understand the root cause. Link: https://community.cyberark.com/s/Submit-a-Case
Thanks,
Tamir
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

