Skip to content
New issue

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

setg broken? #616

Open
dtest505 opened this issue Sep 22, 2019 · 0 comments
Open

setg broken? #616

dtest505 opened this issue Sep 22, 2019 · 0 comments
Labels

Comments

@dtest505
Copy link

! ANY INCOMPLETE REPORT WILL BE CLOSED RIGHT AWAY !

Steps to Reproduce (for bugs)

  1. use X
  2. setg target y
  3. use Z
  4. show options and target is blank.

Your Environment

  • RouterSploit Version used:
  • Operating System and version:
    mac OS X
  • Python Version: ( python3 --version )
    3.7.1
  • Python Environment: ( python3 -m pip freeze )
    appnope==0.1.0
    asn1crypto==0.24.0
    backcall==0.1.0
    backports.functools-lru-cache==1.5
    bcrypt==3.1.7
    certifi==2019.9.11
    cffi==1.12.3
    chardet==3.0.4
    cryptography==2.7
    decorator==4.4.0
    future==0.17.1
    GreatFET==2019.5.1.dev0
    idna==2.8
    ipython==7.5.0
    ipython-genutils==0.2.0
    jedi==0.13.3
    paramiko==2.6.0
    parso==0.4.0
    pexpect==4.7.0
    pickleshare==0.7.5
    ply==3.11
    prompt-toolkit==2.0.9
    ptyprocess==0.6.0
    pyasn1==0.4.7
    pycparser==2.19
    pycryptodome==3.9.0
    pycryptodomex==3.9.0
    Pygments==2.4.2
    pygreat==2019.5.1.dev0
    PyNaCl==1.3.0
    pysmi==0.3.4
    pysnmp==4.4.6
    pyusb==1.0.2
    requests==2.21.0
    six==1.12.0
    traitlets==4.3.2
    urllib3==1.24.3
    wcwidth==0.1.7

Current Behavior

  • If describing a bug, tell us what happens instead of the expected behavior
  • If suggesting a change/improvement, tell us how it works right now

setg not carrying over as global anymore.

Expected Behavior

  • If you're describing a bug, tell us what should happen
  • If you're suggesting a change/improvement, tell us how it should work
@lucyoa lucyoa added the bug label Dec 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants