dafthack / dafthack/MailSniper
Invoke-WebRequest
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 3.3k
- Forks
- 597
- Avg merge
- 1h 11m
- Merged PRs (30d)
- 1
Description
here is the command i typed :
" Invoke-DomainHarvestOWA -ExchHostname "mail.****.com" -DomainList .\domainlist.txt -OutFile potential-domains.txt -Brute"
i have tried without " -Brute " also the same error message
here is the error i got :
" Invoke-WebRequest : The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
At C:\Users\fm2\Desktop\MailSniper-master\MailSniper.ps1:2166 char:21
- ... $owalogin = Invoke-WebRequest -Uri $OWAURL -Method POST -Body $POSTpa ...
-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~- CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
- FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Invoke-WebRequest call at MailSniper.ps1 line 2166 and reproduce the Invoke-DomainHarvestOWA command using the supplied Exchange hostname and domain list. Compare behavior with and without -Brute; done means identifying and documenting or correcting the cause of the closed connection error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100