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

ERROR: type modifier is not allowed for type "bytea" #1605

Closed
Felarof23 opened this issue Aug 9, 2018 · 2 comments
Closed

ERROR: type modifier is not allowed for type "bytea" #1605

Felarof23 opened this issue Aug 9, 2018 · 2 comments

Comments

@Felarof23
Copy link

Felarof23 commented Aug 9, 2018

Verify first that your issue/request has not been posted previously:

Ensure you're using the latest version of BeEF.

Environment

What version/revision of BeEF are you using?
0.4.7.0-alpha

On what version of Ruby?
ruby 2.5.1p57

On what browser?
Chrome

On what operating system?
Linux kali 4.1.19-v7 #1 SMP Tue Mar 15 15:10:00 CDT 2016 armv7l GNU/Linux

Configuration

Are you using a non-default configuration?
yes, driver :postgres

Have you enabled or disabled any BeEF extensions?
yes, metasploit

Summary

Please provide a summary of the issue.

Expected Behaviour

What was the expected result?
run BeEF normally

Actual Behaviour

What was the actual result?
Error when it try to create postgresql database

Steps to Reproduce

Please provide steps to reproduce this issue.

change driver to postgres in config.yaml
change port to 5432 in config.yaml
enable dm-postgres-adapter
successfully bundle install
run ./beef

Additional Information

Please provide any additional information which may be useful in resolving this issue, such as debugging output and relevant screen shots.

Postgresql Version:
psql (10.4 (Debian 10.4-2), server 9.6.5)

image

image

@passbe passbe self-assigned this Sep 27, 2018
@bcoles
Copy link
Collaborator

bcoles commented Feb 25, 2019

I also ran into this a while ago. #932 (comment)

Changing the column type to Text in the extensions/requester/models/http.rb model resolved the issue (at least for plain text).

I'm not sure how well that will work with binary data, but it probably can't make things any worse, as there's other bugs lurking in the requester/proxy code when dealing with binary data, such as #1460.

@wadealcorn wadealcorn added this to the 0.5.0-alpha milestone Sep 16, 2019
@jcrew99 jcrew99 modified the milestones: 0.5.0.0-alpha, 0.6.0.0-alpha May 18, 2020
@bcoles bcoles modified the milestones: 0.5.5.0-alpha, 0.5.6.0-alpha Aug 1, 2022
@bcoles bcoles removed this from the 0.5.6.0-alpha milestone Apr 2, 2023
@bcoles
Copy link
Collaborator

bcoles commented Apr 2, 2023

BeEF now uses ActiveRecord instead of DataMapper, which may (or may not) have resolved this issue.

More importantly, BeEF no longer supports PostgreSQL. We may or may not have to review this issue again in the future if PostgreSQL support is re-added.

Closing.

@bcoles bcoles closed this as completed Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants