We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The IP Stack API key management in Hawk has several usability issues:
%LOCALAPPDATA%\Hawk\Hawk.json
Start-HawkUserInvestigation
access_key
3.2.3
Get-IPGeolocation
Initialize-HawkGlobalObject
[Parameter()] [string]$IPStackAPIKey **Modify Initialization Flow:** - Move API key check to initialization after output folder prompt. - Validate API key input (prevent empty string storage). - Add command-line parameter support. - Add an option to update the existing key. **Update Get-IPGeolocation:** - Improve error handling for missing/invalid keys. - Add validation before API calls. - Provide better error messages directing users to proper key configuration. **Add New Function:** Update-HawkIPStackKey [-Key <string>] **Update HawkAppData Handling:** - Don't store empty strings. - Validate stored keys on load. - Clear invalid configurations. ### Acceptance Criteria _No response_
The text was updated successfully, but these errors were encountered:
dcodev1702
When branches are created from issues, their pull requests are automatically linked.
What happened?
The IP Stack API key management in Hawk has several usability issues:
%LOCALAPPDATA%\Hawk\Hawk.json
.Steps to Reproduce
Start-HawkUserInvestigation
for the first time.%LOCALAPPDATA%\Hawk\Hawk.json
contains an emptyaccess_key
value.Start-HawkUserInvestigation
again.Hawk Version
3.2.3
Technical Analysis
Get-IPGeolocation
execution rather than initialization.Implementation Plan
Add New Parameter to
Initialize-HawkGlobalObject
:The text was updated successfully, but these errors were encountered: