Downloads:
1,193,273
Downloads of v 4.1.2:
84
Last Update:
09 Jan 2020
Package Maintainer(s):
Software Author(s):
- osquery
Tags:
infosec toolsosquery
Downloads:
1,193,273
Downloads of v 4.1.2:
84
Software Author(s):
- osquery
osquery
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This package was rejected on 13 Feb 2020. The reviewer chocolatey-ops has listed the following reason(s):
osquery allows you to easily ask questions about your Linux, macOS, and
Windows infrastructure. Whether your goal is intrusion detection,
infrastructure reliability, or compliance, osquery gives you the ability
to empower and inform a broad set of organizations within your company.
### Package Parameters
* /InstallService
- This creates a new windows service that will auto-start the daemon.
These parameters can be passed to the installer with the user of -params
.
For example: -params '"/InstallService"'
.
md5: AD21026EC8B1DE809B0FF44598E9140B | sha1: 050301A7DA7A41109D9A70C93C62D964743EA4FC | sha256: 00967CC600DE563753294FB3CF649BF83C8345B25940101C0F9732C6276B1A6E | sha512: AAD71CDB15A79CF74C3E90156F4611545C9B5CF2ACCB706F638C2AE6FBF9D23FD39D51D84C62321C5C1438CF804B1CAF5455CE9DE1707B09B8248D81190999E6
# Copyright (c) 2014-present, Facebook, Inc.
# All rights reserved.
#
# This source code is licensed in accordance with the terms specified in
# the LICENSE file found in the root directory of this source tree.
# This library file contains constant definitions and helper functions
#Requires -Version 3.0
. "$PSScriptRoot\\osquery_utils.ps1"
# Ensure the service is stopped and processes are not running if exists.
if ((Get-Service $serviceName -ErrorAction SilentlyContinue) -and `
(Get-Service $serviceName).Status -eq 'Running') {
Stop-Service $serviceName
# If we find zombie processes, ensure they're termintated
$proc = Get-Process | Where-Object { $_.ProcessName -eq 'osqueryd' }
if ($null -ne $proc) {
Stop-Process -Force $proc -ErrorAction SilentlyContinue
}
}
# Lastly, ensure that the Deny Write ACLs have been removed before modifying
if (Test-Path $daemonFolder) {
Set-DenyWriteAcl $daemonFolder 'Remove'
}
if (Test-Path $extensionsFolder) {
Set-DenyWriteAcl $extensionsFolder 'Remove'
}
# Copyright (c) 2014-present, Facebook, Inc.
# All rights reserved.
#
# This source code is licensed in accordance with the terms specified in
# the LICENSE file found in the root directory of this source tree.
# This library file contains constant definitions and helper functions
#Requires -Version 3.0
. "$PSScriptRoot\\osquery_utils.ps1"
# Remove the osquery path from the System PATH variable. Note: Here
# we don't make use of our local vars, as Regex requires escaping the '\'
$oldPath = [System.Environment]::GetEnvironmentVariable('Path', 'Machine')
if ($oldPath -imatch [regex]::escape($targetFolder)) {
$newPath = $oldPath -replace [regex]::escape($targetFolder), $NULL
[System.Environment]::SetEnvironmentVariable('Path', $newPath, 'Machine')
}
if ((Get-Service $serviceName -ErrorAction SilentlyContinue)) {
Stop-Service $serviceName
# If we find zombie processes, ensure they're termintated
$proc = Get-Process | Where-Object { $_.ProcessName -eq 'osqueryd' }
if ($null -ne $proc) {
Stop-Process -Force $proc -ErrorAction SilentlyContinue
}
Set-Service $serviceName -startuptype 'manual'
Get-CimInstance -ClassName Win32_Service -Filter "Name='osqueryd'" | Invoke-CimMethod -methodName Delete
}
if (Test-Path $targetFolder) {
Remove-Item -Force -Recurse $targetFolder
} else {
Write-Debug 'osquery was not found on the system. Nothing to do.'
}
# License
By contributing to osquery you agree that your contributions will be licensed
under the terms of both the [LICENSE-Apache-2.0](LICENSE-Apache-2.0) and the
[LICENSE-GPL-2.0](LICENSE-GPL-2.0) files in the root of this source tree.
If you're using osquery you are free to choose one of the provided licenses.
`SPDX-License-Identifier: Apache-2.0 OR GPL-2.0-only`
# Copyright (c) 2014-present, Facebook, Inc.
# All rights reserved.
#
# This source code is licensed in accordance with the terms specified in
# the LICENSE file found in the root directory of this source tree.
# Force Powershell to use TLS 1.2
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls12
# The osquery installation happens in Program Files
$progFiles = [System.Environment]::GetEnvironmentVariable('ProgramFiles')
$targetFolder = Join-Path $progFiles 'osquery'
# Maintain the daemon and extension folders for "safe" permissions management
$daemonFolder = Join-Path $targetFolder 'osqueryd'
$extensionsFolder = Join-Path $targetFolder 'extensions'
$logFolder = Join-Path $targetFolder 'log'
# Maintain the binary paths for creating the system service and extraction
$targetDaemonBin = Join-Path $targetFolder "osqueryd.exe"
$destDaemonBin = Join-Path $daemonFolder "osqueryd.exe"
# Meta data for the system service installation
$serviceName = 'osqueryd'
$serviceDescription = 'osquery daemon service'
# Track the old installation paths for removal
$progData = [System.Environment]::GetEnvironmentVariable('ProgramData')
$legacyInstall = Join-Path $progData "osquery"
# Helper function to add an explicit Deny-Write ACE for the Everyone group
function Set-DenyWriteAcl {
[CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = "Medium")]
[OutputType('System.Boolean')]
param(
[string] $targetDir = '',
[string] $action = ''
)
if (($action -ine 'Add') -and ($action -ine 'Remove')) {
Write-Debug '[-] Invalid action in Set-DenyWriteAcl.'
return $false
}
if ($PSCmdlet.ShouldProcess($targetDir)) {
$acl = Get-Acl $targetDir
$inheritanceFlag = [System.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [System.Security.AccessControl.InheritanceFlags]::ObjectInherit
$propagationFlag = [System.Security.AccessControl.PropagationFlags]::None
$permType = [System.Security.AccessControl.AccessControlType]::Deny
$worldSIDObj = New-Object System.Security.Principal.SecurityIdentifier ('S-1-1-0')
$worldUser = $worldSIDObj.Translate([System.Security.Principal.NTAccount])
$permission = $worldUser.Value, "write", $inheritanceFlag, $propagationFlag, $permType
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission
# We only support adding or removing the ACL
if ($action -ieq 'add') {
$acl.SetAccessRule($accessRule)
} else {
$acl.RemoveAccessRule($accessRule)
}
Set-Acl $targetDir $acl
return $true
}
return $false
}
# A helper function to set "safe" permissions for osquery binaries
function Set-SafePermissions {
[CmdletBinding(SupportsShouldProcess = $true, ConfirmImpact = "Medium")]
[OutputType('System.Boolean')]
param(
[string] $target = ''
)
if ($PSCmdlet.ShouldProcess($target)) {
$acl = Get-Acl $target
# First, to ensure success, we remove the entirety of the ACL
$acl.SetAccessRuleProtection($true, $false)
foreach ($access in $acl.Access) {
$acl.RemoveAccessRule($access)
}
Set-Acl $target $acl
$acl = Get-Acl $target
$inheritanceFlag = [System.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [System.Security.AccessControl.InheritanceFlags]::ObjectInherit
$propagationFlag = [System.Security.AccessControl.PropagationFlags]::None
$permType = [System.Security.AccessControl.AccessControlType]::Allow
# "Safe" permissions in osquery entail the containing folder and binary both
# are owned by the Administrators group, as well as no account has Write
# permissions except for the Administrators group and SYSTEM account
$systemSid = New-Object System.Security.Principal.SecurityIdentifier('S-1-5-18')
$systemUser = $systemSid.Translate([System.Security.Principal.NTAccount])
$adminsSid = New-Object System.Security.Principal.SecurityIdentifier('S-1-5-32-544')
$adminsGroup = $adminsSid.Translate([System.Security.Principal.NTAccount])
$usersSid = New-Object System.Security.Principal.SecurityIdentifier('S-1-5-32-545')
$usersGroup = $usersSid.Translate([System.Security.Principal.NTAccount])
$permGroups = @($systemUser, $adminsGroup, $usersGroup)
foreach ($accnt in $permGroups) {
$grantedPerm = ''
if ($accnt -eq $usersGroup) {
$grantedPerm = 'ReadAndExecute'
} else {
$grantedPerm = 'FullControl'
}
$permission = $accnt.Value, $grantedPerm, $inheritanceFlag, $propagationFlag, $permType
$accessRule = New-Object System.Security.AccessControl.FileSystemAccessRule $permission
$acl.SetAccessRule($accessRule)
}
$acl.SetOwner($adminsGroup)
Set-Acl $target $acl
# Finally set the Administrators group as the owner for all items
$items = Get-ChildItem -Recurse -Path $target
foreach ($item in $items) {
$acl = Get-Acl -Path $item.FullName
$acl.SetOwner($adminsGroup)
Set-Acl $item.FullName $acl
}
return $true
}
return $false
}
# Helper function for running a .bat file from powershell
function Invoke-BatchFile {
param(
[string]$path,
[string]$parameters
)
$tempFile = [IO.Path]::GetTempFileName()
cmd.exe /c " `"$path`" $parameters && set > `"$tempFile`" "
Get-Content $tempFile | Foreach-Object {
if ($_ -match '^(.*?)=(.*)$') {
Set-Content "env:\$($matches[1])" $matches[2]
}
}
Remove-Item $tempFile
}
# Constructs a chocolatey .nuspec file in the current directory
function Write-NuSpec {
param(
[string] $packageName,
[string] $version,
[string] $authors,
[string] $owners,
[string] $projectSource,
[string] $packageSourceUrl,
[string] $copyright,
[string] $license
)
$nuspec = @"
<?xml version="1.0" encoding="utf-8"?>
<!-- Do not remove this test for UTF-8: if “Ω” doesn’t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->
<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
<metadata>
<id>$packageName</id>
<title>$packageName</title>
<version>$version</version>
<authors>$authors</authors>
<owners>$owners</owners>
<summary>$packageName</summary>
<description>$packageName</description>
<projectUrl>$projectSource</projectUrl>
<packageSourceUrl>$packageSourceUrl</packageSourceUrl>
<tags>$packageName</tags>
<copyright>$copyright</copyright>
<licenseUrl>$license</licenseUrl>
<requireLicenseAcceptance>false</requireLicenseAcceptance>
</metadata>
<files>
<file src="local\**" target="local" />
</files>
</package>
"@
Out-File -Encoding "UTF8" -FilePath "$packageName.nuspec" -InputObject $nuspec
}
# Derive the location of the osquery build location
function Get-OsqueryBuildPath {
[OutputType('System.String')]
param()
$loc = Get-Location
$toks = $loc -Split '\\'
$ret = ''
0..$toks.length | ForEach-Object {
if (Test-Path "$($toks[0..$_] -Join '\')\tools\provision.ps1") {
$ret = "$($toks[0..$_] -Join '\')\build"
}
}
return $ret
}
# Helper function to add to the SYSTEM path
function Add-ToSystemPath {
param(
[string] $targetFolder = ''
)
$oldPath = [System.Environment]::GetEnvironmentVariable('Path', 'Machine')
if (-not ($oldPath -imatch [regex]::escape($targetFolder))) {
$newPath = $oldPath
if ($oldPath[-1] -eq ';') {
$newPath = $newPath + $targetFolder
} else {
$newPath = $newPath + ';' + $targetFolder
}
[System.Environment]::SetEnvironmentVariable('Path', $newPath, 'Machine')
}
}
# A helper function for starting and waiting on processes in powershell
function Start-OsqueryProcess {
param(
[string] $binaryPath = '',
[array] $binaryArgs = @(),
[bool] $redirectOutput = $true
)
$pinfo = New-Object System.Diagnostics.ProcessStartInfo
$pinfo.FileName = $binaryPath
$pinfo.RedirectStandardError = $redirectOutput
$pinfo.RedirectStandardOutput = $redirectOutput
$pinfo.UseShellExecute = $false
$pinfo.Arguments = $binaryArgs
$pinfo.WorkingDirectory = Get-Location
$p = New-Object System.Diagnostics.Process
$p.StartInfo = $pinfo
$p.Start()
$p.WaitForExit()
if ($redirectOutput) {
$stdout = $p.StandardOutput.ReadToEnd()
$stderr = $p.StandardError.ReadToEnd()
$exit = $p.ExitCode
[PSCustomObject] @{
stdout = $stdout
stderr = $stderr
exitcode = $exit
}
} else {
$exit = $p.ExitCode
[PSCustomObject] @{
exitcode = $exit
}
}
}
# A helper function to derive the latest VS install
function Get-VSInfo {
# Attempt to make use of vswhere to derive the build tools scripts
$vswhere = (Get-Command 'vswhere').Source
$vswhereArgs = @('-latest', '-legacy')
$vswhereOut = (Start-OsqueryProcess $vswhere $vswhereArgs).stdout
$vsinfo = New-Object -TypeName psobject
$vsinfo | Add-Member -MemberType NoteProperty -Name version -Value ''
$vsinfo | Add-Member -MemberType NoteProperty -Name location -Value ''
foreach ($l in $vswhereOut.split([environment]::NewLine)) {
$toks = $l.split(":")
if ($toks.Length -lt 2) {
continue
}
if ($toks[0].trim() -like 'installationVersion') {
$vsinfo.version = $toks[1].Split(".")[0]
}
if ($toks[0].trim() -like 'installationPath') {
$vsinfo.location = [System.String]::Join(":", $toks[1..$toks.Length])
}
}
$vsinfo.location = $vsinfo.location.trim()
$vsinfo.version = $vsinfo.version.trim()
return $vsinfo
}
# A helper function to derive the latest VS install and call vcvarsall.bat
function Invoke-VcVarsAll {
$vsinfo = Get-VSInfo
$vsLoc = $vsinfo.location
$vsVersion = $vsinfo.version
if ($vsLoc -ne '') {
$vcvarsall = Join-Path $vsLoc 'VC'
if ($vsVersion -eq '15') {
$vcvarsall = Join-Path $vcvarsall '\Auxiliary\Build\vcvarsall.bat'
} else {
$vcvarsall = Join-Path $vcvarsall 'vcvarsall.bat'
}
# Lastly invoke the environment provisioning script
$null = Invoke-BatchFile "$vcvarsall" "amd64"
return $true
}
# As a last ditch effort, attempt to find the env variables set by VS2015
# in order to derive the location of vcvarsall
$vsComnTools = [environment]::GetEnvironmentVariable("VS140COMNTOOLS")
if ($vsComnTools -eq '') {
return $false
}
$vcvarsall = Resolve-Path $(Join-Path "$vsComnTools" "..\..\VC")
$vcvarsall = Join-Path $vcvarsall 'vcvarsall.bat'
$null = Invoke-BatchFile "$vcvarsall" "amd64"
return $true
}
To verify the osquery binaries are valid and not corrupted, one can run one of the following:
C:\Users\> Get-FileHash -Algorithm SHA256 C:\Program Files\osquery\osqueryd\osqueryd.exe
C:\Users\> Get-FileHash -Algorithm SHA1 C:\Program Files\osquery\osqueryd\osqueryd.exe
C:\Users\> Get-FileHash -Algorithm MD5 C:\Program Files\osquery\osqueryd\osqueryd.exe
And verify that the digests match one of the below values:
SHA256: 4AE3EDFD462AB11204FD318C5550F8E0414DF4820076A0A3C3842038C8CB0D7C
SHA1: 68B253E4846FD6A769ADCB5990F2472B3AE28368
MD5: 0370CE7A13EFD26ADD63C7BBEDE504FB
Log in or click on link to see number of positives.
- osqueryd.exe (4ae3edfd462a) - ## / 67
- osquery.4.1.2.nupkg (604bbde2e0d4) - ## / 63
- osquery.zip (00967cc600de) - ## / 63
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
osquery 5.11.0 | 40424 | Thursday, January 25, 2024 | Approved | |
osquery 5.10.2 | 192 | Thursday, January 25, 2024 | Approved | |
osquery 5.9.1 | 40 | Thursday, January 25, 2024 | Approved | |
osquery 5.8.2 | 116580 | Friday, May 12, 2023 | Approved | |
osquery 5.7.0 | 22938 | Tuesday, March 28, 2023 | Approved | |
osquery 5.6.0 | 550 | Tuesday, March 28, 2023 | Approved | |
osquery 5.5.1 | 46104 | Saturday, January 7, 2023 | Approved | |
osquery 5.4.0 | 95089 | Thursday, September 8, 2022 | Approved | |
osquery 5.3.0 | 880 | Thursday, September 8, 2022 | Approved | |
osquery 5.2.3 | 267 | Thursday, September 8, 2022 | Approved | |
osquery 5.2.2 | 144646 | Tuesday, March 15, 2022 | Approved | |
osquery 5.2.1 | 40069 | Tuesday, January 25, 2022 | Approved | |
osquery 5.2.0 | 17293 | Thursday, January 6, 2022 | Approved | |
osquery 5.1.0 | 324 | Thursday, January 6, 2022 | Approved | |
osquery 5.0.1 | 122433 | Thursday, September 16, 2021 | Approved | |
osquery 4.9.0 | 1211 | Wednesday, September 15, 2021 | Approved | |
osquery 4.8.0 | 32288 | Monday, May 3, 2021 | Approved | |
osquery 4.7.0 | 4231 | Tuesday, April 20, 2021 | Approved | |
osquery 4.6.0.2 | 16232 | Friday, February 12, 2021 | Approved | |
osquery 4.5.1 | 20315 | Monday, November 9, 2020 | Approved | |
osquery 4.5.0 | 10263 | Thursday, October 1, 2020 | Approved | |
osquery 4.4.0 | 13112 | Friday, July 31, 2020 | Approved | |
osquery 4.3.0 | 20985 | Saturday, May 9, 2020 | Approved | |
osquery 4.2.0 | 29319 | Tuesday, February 25, 2020 | Approved | |
osquery 4.0.2 | 58612 | Friday, September 13, 2019 | Approved | |
osquery 4.0.1 | 600 | Wednesday, September 11, 2019 | Approved | |
osquery 3.4.0 | 9879 | Thursday, May 23, 2019 | Approved | |
osquery 3.3.2 | 120465 | Monday, January 28, 2019 | Approved | |
osquery 3.3.1 | 43669 | Tuesday, October 2, 2018 | Approved | |
osquery 3.3.0 | 3341 | Monday, August 20, 2018 | Approved | |
osquery 3.2.9 | 74810 | Monday, July 2, 2018 | Approved | |
osquery 3.2.6 | 52855 | Monday, July 2, 2018 | Approved | |
osquery 3.2.4 | 3136 | Friday, May 4, 2018 | Approved | |
osquery 2.11.2 | 5772 | Monday, February 5, 2018 | Approved | |
osquery 2.11.0 | 2079 | Friday, January 12, 2018 | Approved | |
osquery 2.10.4 | 1893 | Sunday, December 3, 2017 | Approved | |
osquery 2.10.2 | 1149 | Thursday, November 16, 2017 | Approved | |
osquery 2.9.0 | 2551 | Friday, October 20, 2017 | Approved | |
osquery 2.8.0 | 1399 | Wednesday, September 27, 2017 | Approved | |
osquery 2.7.0 | 1508 | Wednesday, August 23, 2017 | Approved | |
osquery 2.6.1 | 954 | Sunday, August 6, 2017 | Approved | |
osquery 2.6.0 | 664 | Friday, July 28, 2017 | Approved | |
osquery 2.5.0 | 4678 | Tuesday, June 20, 2017 | Approved | |
osquery 2.4.2 | 1490 | Tuesday, May 9, 2017 | Approved | |
osquery 2.4.0 | 888 | Saturday, April 15, 2017 | Approved | |
osquery 2.3.2 | 1563 | Thursday, February 16, 2017 | Approved | |
osquery 2.2.1 | 838 | Thursday, December 22, 2016 | Approved | |
osquery 2.2.1-gd6630be | 485 | Tuesday, December 27, 2016 | Exempted | |
osquery 2.2.0 | 535 | Tuesday, December 13, 2016 | Approved | |
osquery 2.1.1 | 708 | Thursday, November 3, 2016 | Approved | |
osquery 2.0.0 | 764 | Tuesday, October 11, 2016 | Approved |
Copyright (c) 2014-present, Facebook, Inc. All rights reserved.
This package has no dependencies.
Ground Rules:
- This discussion is only about osquery and the osquery package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or osquery, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
thor (maintainer) on 09 Jan 2020 06:45:02 +00:00:
User 'thor' (maintainer) submitted package.
chocolatey-ops (reviewer) on 09 Jan 2020 07:17:05 +00:00:
osquery has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
packageSourceUrl
, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
chocolatey-ops (reviewer) on 09 Jan 2020 07:20:10 +00:00:
osquery has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/587d0c1ecdb48059ac1a5c250a2930c9 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 29 Jan 2020 07:22:16 +00:00:
We've found osquery v4.1.2 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 13 Feb 2020 07:23:32 +00:00:
Unfortunately there has not been progress to move osquery v4.1.2 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.