[Alan Turing]

While some members here know about buffer overflows and other "advanced" exploitation methods., most people here haven't even heard of bof.

Ah oh well, hopefully this makes OP realize something, and puts out a better tutorial.

[JacobBaker]

Very useful, thanks alot broski!

[Alan Turing]

Very useful, thanks alot broski!

It's not really all that useful, besides the knowledge. But do you actually understand what the attack is and how it's used, as oppose to setting LHOST, LPORT, RHOST and typing "Exploit"?

That's a key point.

[adriancs35]

i got this error while connecting pgadmin at step 3

Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432? could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?
If you encounter this message, please check if the server you're trying to contact is actually running PostgreSQL on the given port. Test if you have network connectivity from your client to the server host using ping or equivalent tools. Is your network / VPN / SSH tunnel / firewall configured correctly?
For security reasons, PostgreSQL does not listen on all available IP addresses on the server machine initially. In order to access the server over the network, you need to enable listening on the address first.
For PostgreSQL servers starting with version 8.0, this is controlled using the "listen_addresses" parameter in the postgresql.conf file. Here, you can enter a list of IP addresses the server should listen on, or simply use '*' to listen on all available IP addresses. For earlier servers (Version 7.3 or 7.4), you'll need to set the "tcpip_socket" parameter to 'true'.
You can use the postgresql.conf editor that is built into pgAdmin III to edit the postgresql.conf configuration file. After changing this file, you need to restart the server process to make the setting effective.
If you double-checked your configuration but still get this error message, it's still unlikely that you encounter a fatal PostgreSQL misbehaviour. You probably have some low level network connectivity problems (e.g. firewall configuration). Please check this thoroughly before reporting a bug to the PostgreSQL community.

[Alan Turing]

This thread is seriously the worst

[trinity]

Great. now teach me the same but how you would do it over WAN.

[Nebulous]

Great. now teach me the same but how you would do it over WAN.

Please stop posting on year old threads to increase your post count. It makes you look annoying.

[warstrike]

nice tootorial bro i have fuckered many box with your help bro

[dotz]

Damn... have to see this one out

[darkcast]

Just another metasploit autopwn tutorial, move along folks.

Agreed !!