sensepost / sensepost/objection

Ability to set Corporate proxy settings due to jarsigner [Feature Request]

Open
#75 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

✨enhancement
Dominant language
Python
Stars
9.4k
Forks
1k
Avg merge
14d 5h
Merged PRs (30d)
1

Description

Corporate proxy settings can be set with the below bash script:

#!/bin/bash
export REQUESTS_CA_BUNDLE=/home/$USER/cacert.pem
export http_proxy=http://...:8080
export https_proxy=https://
...:8080
echo "Shell setup for Corporate Proxy"

The problem is jarsigner does not use these environment variables. See below:

Signing the new APK may have failed.
jarsigner: unable to sign jar: no response from the Timestamping Authority. When connecting from behind a firewall an HTTP or HTTPS proxy may need to be specified. Supply the following options to jarsigner:
  -J-Dhttp.proxyHost=<hostname>
  -J-Dhttp.proxyPort=<portnumber>
or
  -J-Dhttps.proxyHost=<hostname> 
  -J-Dhttps.proxyPort=<portnumber> 


Signed the new APK

-J-Dhttps.proxyHost=..*. -J-Dhttps.proxyPort=8080 can't be passed to Objection as an option and as far as I can see from reading online there is not a config file where these settings can be added to for jarsigner.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing Objection's APK signing path and how it invokes jarsigner; the issue names no source file or test entry point. Review how the documented -J-Dhttp.proxyHost, -J-Dhttp.proxyPort, -J-Dhttps.proxyHost, and -J-Dhttps.proxyPort values could be supplied, then verify that signing works behind a corporate proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, python
Domain
mobile-dev, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.