Page 4 of 6 FirstFirst ... 23456 LastLast
Results 31 to 40 of 54

Thread: Metasploit db_autopwn using PostgreSQL

  1. #31
    Just burned his ISO
    Join Date
    Feb 2010
    Location
    505
    Posts
    10

    Default Re: Metasploit db_autopwn using PostgreSQL

    Quote Originally Posted by fungi View Post

    So how can I set that as the default when starting msf? Like running msf from fast-track?
    Seriously? It's all in the .rc files. You can do everything you want to automate in there.

    Metasploit: Automating the Metasploit Console

  2. #32
    Just burned his ISO
    Join Date
    Jun 2010
    Posts
    7

    Default Re: Metasploit db_autopwn using PostgreSQL

    Oh thank you! Who knew it would be so obvious!

    This is a much better explanation - the only thing missing is commenting out the ssl=true

    Metasploit Framework - Setting Up a Database - Metasploit Redmine Interface

    also with details on how to enable the mentioned options by default

    Code:
    $ cat > ~/.msf3/msfconsole.rc
    db_driver postgresql
    db_connect msf:r4nd0m@127.0.0.1/msf
    db_workspace -a MyProject
    ^D

  3. #33
    Just burned his ISO
    Join Date
    Jan 2008
    Posts
    6

    Default Re: Metasploit db_autopwn using PostgreSQL

    i m doing like this:

    ./msfconsole
    db_driver
    db_create targets
    db_nmap IP -p PORT
    db_autopwn -t -s -e -p -b


    This working fine for me ...

  4. #34
    Just burned his ISO
    Join Date
    Jan 2010
    Posts
    20

    Default Re: Metasploit db_autopwn using PostgreSQL

    I finally got my Postgresql to work in Metsploit, what I did in the end was to fire up synaptic and remove 'framework 3' and then I downloaded the installer from the metasploit website, installed metasploit 3.4.1 from that, updated it and fired up msfconsle and hey presto working postgres.

    I noticed from the metsploit website that the devs had fixed an issue with shipping a working gem postgresql Bug#1879.

    Hope this helps any others who have been 'fighting' with this one.

  5. #35
    Just burned his ISO
    Join Date
    Aug 2010
    Posts
    1

    Default Re: Metasploit db_autopwn using PostgreSQL

    Whenever i want to do something in linux, even if its something small, it costs me my whole day. This is also the case with creating a simple database for msf3.

    Is this like a newbie-test ?

    I cant get the driver to work. I do everything followed in the tutorial. I do:

    Code:
    db_connect postgres:postgres PASSWORD@127.0.0.1/msf3
    Error while running command db_connect failed to connect to database: FATAL: Ident authentication failed for user "root".
    Someone enlighten me.

  6. #36
    Administrator sickness's Avatar
    Join Date
    Jan 2010
    Location
    Behind the screen.
    Posts
    2,921

    Default Re: Metasploit db_autopwn using PostgreSQL

    The command is:
    Code:
    db_connect postgres:PASSWORD@127.0.0.1/metasploit
    And postgreSQL must be turned on before you connect to it.
    Back|track giving machine guns to monkeys since 2007 !

    Do not read the Wiki, most your questions will not be answered there !
    Do not take a look at the: Forum Rules !

  7. #37
    Just burned his ISO
    Join Date
    Oct 2010
    Posts
    1

    Default Re: Metasploit db_autopwn using PostgreSQL

    i just wanted to say thanks to the OP, this tutorial got my metasploit working. i was racking my brain for hours trying to get it to work. you're a champion

  8. #38
    Just burned his ISO
    Join Date
    Feb 2010
    Posts
    3

    Default Re: Metasploit db_autopwn using PostgreSQL

    Thanx for the tut.

    I'm not an expert on databases, and I have not tried this myself. NeXpose integrates very nicely with Metasploit but the installer installs its own PostgreSQL database. If I remember correctly (from a previous install where I used sqlite3 with metasploit) that stops the original database from starting. Thus "/etc/init.d/postgresql-8.3 start" fails.

    Can anyone please comment on that?

  9. #39
    Administrator sickness's Avatar
    Join Date
    Jan 2010
    Location
    Behind the screen.
    Posts
    2,921

    Default Re: Metasploit db_autopwn using PostgreSQL

    pluto I don't really know for sure but if you are talking about using NeXpose from msfconsole I think you can create your own database and use that too
    Back|track giving machine guns to monkeys since 2007 !

    Do not read the Wiki, most your questions will not be answered there !
    Do not take a look at the: Forum Rules !

  10. #40
    Member
    Join Date
    Feb 2010
    Location
    MTI3LjAuMC4x
    Posts
    90

    Default Re: Metasploit db_autopwn using PostgreSQL

    just updated to R1 if you have this problem here is the fix...

    Code:
    2010-11-07 13:49:00 PST FATAL:  could not create lock file "/var/run/postgresql/.s.PGSQL.5432.lock": Permission denied
    edit /etc/postgresql/8.3/main/postgresql.conf
    Code:
    external_pid_file = '/tmp/8.3-main.pid'    
    unix_socket_directory = '/tmp/'
    #ssl = true (dont forget that from the OP)
    also just a informational for the how-to you can also install
    apt-get install pgadmin3

    if your like me and dont like to deal with command line database managment

    or you can alternately give posgres permissions everywhere either way.. this was just faster
    Last edited by spudgunman; 11-07-2010 at 10:23 PM. Reason: added pgadmin info

Page 4 of 6 FirstFirst ... 23456 LastLast

Similar Threads

  1. Nexpose Postgresql error
    By WolverineOD in forum Beginners Forum
    Replies: 1
    Last Post: 05-02-2010, 04:45 PM
  2. apt-get upgrade: Fehler bzgl postgresql-8.3
    By cleguevara in forum Software support
    Replies: 4
    Last Post: 01-13-2010, 08:55 AM
  3. errore: postgresql-8.3
    By xanders in forum Supporto Software
    Replies: 10
    Last Post: 11-21-2009, 09:34 AM
  4. Error with Postgresql after recent dist-upgrade
    By imported_davehardy20 in forum OLD BackTrack 4 Bugs and Fixes
    Replies: 15
    Last Post: 11-20-2009, 10:23 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •