Rspec error in bitlocker

Green-m commented 5 years ago

Steps to reproduce

How'd you do it?

Run rpsec to test code.

Expected behavior

All tests pass.

Current behavior

Rex::Parser::BITLOCKER F

  1) Rex::Parser::BITLOCKER Extract and decrypt recovery key from recovery password
     Failure/Error: ccm = OpenSSL::CCM.new('AES',  key, 16)

     OpenSSL::CCMError:
       unsupported cipher algorithm (AES)
     # /Users/green/.rvm/gems/ruby-2.5.3@metasploit-framework/gems/openssl-ccm-1.2.1/lib/openssl/ccm.rb:42:in `initialize'
     # ./lib/rex/parser/fs/bitlocker.rb:111:in `new'
     # ./lib/rex/parser/fs/bitlocker.rb:111:in `decrypt_aes_ccm_key'
     # ./lib/rex/parser/fs/bitlocker.rb:87:in `block (2 levels) in vmk_from_recovery_password'
     # ./lib/rex/parser/fs/bitlocker.rb:86:in `each'
     # ./lib/rex/parser/fs/bitlocker.rb:86:in `block in vmk_from_recovery_password'
     # ./lib/rex/parser/fs/bitlocker.rb:84:in `each'
     # ./lib/rex/parser/fs/bitlocker.rb:84:in `vmk_from_recovery_password'
     # ./lib/rex/parser/fs/bitlocker.rb:101:in `fvek_from_recovery_password'
     # ./lib/rex/parser/fs/bitlocker.rb:74:in `fvek_from_recovery_password_dislocker'
     # ./spec/lib/rex/parser/fs/bitlocker_spec.rb:89:in `block (2 levels) in <top (required)>'

System stuff

Metasploit version

Get this with the version command in msfconsole (or git log -1 --pretty=oneline for a source install).

I installed Metasploit with:

[ ] Kali package via apt
[ ] Omnibus installer (nightly)
[ ] Commercial/Community installer (from http://www.rapid7.com/products/metasploit/download.jsp)

[x] Source install (please specify ruby version)

$ ./msfconsole -v
Framework Version: 5.0.0-dev-a457973702
$ ruby -v
ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin17]

OS

What OS are you running Metasploit on?

macos 10.13.6

github-actions[bot] commented 3 years ago

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

github-actions[bot] commented 3 years ago

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

rapid7 / metasploit-framework