Open ghost opened 6 years ago
Does no one know how to do this? At least can someone point me in the direction of proper documentation/research? I've practically been living on this GitHub for the last three weeks, and I've seen nothing about proper plugin compilation... To reiterate, I'm just trying to compile this, which is the stock DoS plugin to ensure that I can compile the plugins correctly. @koeppea maybe you can help me?
the easiest way is to put the source code file under a dedicate folder under plug-ins directory of ettercap's source tree. then add it to the PLUGINS list in plug-ins/CMakeLists.txt. Then your plugin should compile and link correctly when you rebuild ettercap using make within the build directory.
You can also watch out for me in our IRC channel. I'll be there for the next hour.
I'm named format_c in IRC.
@koeppea I gave that a shot, and now I see it linked correctly. Unfortunately, however, it's not showing up in the "plugins" list in Ettercap, and when I try to load it, it says that the plugin has already been loaded. Any idea how to add it to the plugins within Ettercap? Thanks!
Commit your changes in your fork of Ettercap and I can have a look.
@koeppea It looks like I figured it out again! I had forgotten to change the name and description of the attack within the C code. Thank again for your help! It was invaluable!
@Schnuggs
Hey, how is your plugin performing so far? If it's worth the name you gave it, it could very well be part of ettercap.
Can I interest you in sharing the plugin with the rest of us?
On Mar 19, 2018, at 6:01 PM, Schnuggs notifications@github.com wrote:
@koeppea It looks like I figured it out again! I had forgotten to change the name and description of the attack within the C code. Thank again for your help! It was invaluable!
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
@sgeto I’d love to! It’s basically just a variation of a DoS attack where the flooding is done in intervals, making mitigation more difficult. I’ll give you guys the source when I’m done, but I’m only really editing your own dos_attack.c file a little bit.
Don't worry. Improving an existing plugin is just as valuable as creating a new one. If you're happy with your result, let us know, or, even better, open a pull request and we take it from there.
Looking forward to hear from you.
On Mar 21, 2018, at 1:16 AM, Schnuggs notifications@github.com wrote:
@sgeto I’d love to! It’s basically just a variation of a DoS attack where the flooding is done in intervals, making mitigation more difficult. I’ll give you guys the source when I’m done, but I’m only really editing your own dos_attack.c file a little bit.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
@sgeto what branch should I make the pull request for?
ettercap/master
On Mar 22, 2018, at 5:37 PM, Schnuggs notifications@github.com wrote:
@sgeto what branch should I make the pull request for?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
So we're good to close this issue?
@koeppea I believe we are good to close it.
@sgeto for some reason, my git commands are all messed up, so I'll attach the pulse_attack.c source code here. You'll have to add it to the CMakeLists to compile it and make a dedicated folder called pulse_attack. Additionally, I'm uploading it as a TXT file, so you'll have to put the code into a C file. pulse_attack.txt
Sorry!
Just renamed this issue. We'll keep it here but won't schedule it for the upcoming release, since the upcoming release's goal ist to focus on code maintenance and not on new features. We'll pick this up when all the efforts for the new release are done. Then we'll serve this into a dedicated pull reuqest on your behalf.
@sgeto different opinion?
That sounds great! Shoot me an email when it’s up :) also let me know how it works in your tests!
Nope. Exactly my thoughts.
"We are saddened by a bird's cry, but not for a fish's blood. Blessed are those with voices."
-Mamoru Oshii
On Apr 6, 2018, at 1:48 AM, Alexander Köppe notifications@github.com wrote:
Just renamed this issue. We'll keep it here but won't schedule it for the upcoming release, since the upcoming release's goal ist to focus on code maintenance and not on new features. We'll pick this up when all the efforts for the new release are done. Then we'll serve this into a dedicated pull reuqest on your behalf.
@sgeto different opinion?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Wrote a plugin, tried to compile it into a .so with the command
gcc -shared -o libhello.so -fPIC hello.c
, which seemed to work (it put the .so file in the same directory as the .c file. For some reason, though, when I go to load the plugin, Ettercap crashes without a report or anything. Here's the plugin I'm working on:Is there a better way to accomplish this? Thanks so much!