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
With the current form of the script, it would error out when uploading the ear file with the following message:
Uploading EAR file... Traceback (most recent call last): 4: from me.rb:360:in <main>' 3: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:107:in pack' 2: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:107:in each' 1: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:109:in block in pack' /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/blocks.rb:119:in pack': undefined method blank?' for nil:NilClass (NoMethodError)
<main>' 3: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:107:in
each' 1: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:109:in
pack': undefined method
I was able to resolve this and get the exploit working by requiring the ActiveSupport gem (require 'active_support').
The text was updated successfully, but these errors were encountered:
No branches or pull requests
With the current form of the script, it would error out when uploading the ear file with the following message:
Uploading EAR file...
Traceback (most recent call last):
4: from me.rb:360:in
<main>' 3: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:107:in
pack'2: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:107:in
each' 1: from /var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/archive.rb:109:in
block in pack'/var/lib/gems/2.7.0/gems/librex-0.0.999/lib/rex/zip/blocks.rb:119:in
pack': undefined method
blank?' for nil:NilClass (NoMethodError)I was able to resolve this and get the exploit working by requiring the ActiveSupport gem (require 'active_support').
The text was updated successfully, but these errors were encountered: