[Feature Request] Dotnet 5 + comptability

[mynameisORIG]

Feature Request or Bug
Feature Request

**Describe the feature request **
Will there be comparability with the newer versions of Dotnet? It seems like Covenant requires 3.1 dotnet has reached EOL and is unsupported by Windows. Covenant is a great tool, and I would like to not have to do other methods for a C2 server.

[rasta-mouse]

.NET 5 is also EOL now. The current LTS versions are 6 and 8.

Covenant is a C2 framework that provides a collection of the most useful post-exploitation modules, that are competitive to many current C2 frameworks!

But due to its non-maintenance and ignorance by developers, it's lacking many functions and losing its popularity

I am one of the few people who still uses covenant in his Engagements whereas others are using modern C2s like Havoc

For smooth functioning, I have modified 20% of its source code to meet my requirements, but as I am not a person who has advanced knowledge of C# I can't modify it from start to end

With just some of the updates and adding 2-3 features it will gain its popularity back

Below are some:-

1) Adding support to latest .NET version

2) Updating it's dependencies

3) Using latest Roslyn version for compilations

    4) Adding two methods for task "Exit" i.e "Exit Process" and "Exit thread" :- Because when delivering Grunt within a Packer then the Exit Task only terminates it's thread. Hence the Grunt Terminates but the Packer process still continues. So, Adding Two options for Exit Task makes easy for operator to choose which is required at the current situation

    5) Schedule Tasks :- Adding the Schedule Tasks option to schedule the execution of tasks like on first callback or on a specified time

    6) Adding Stability to Grunt Templates:- When payload is executed from a new device (as a victim) for the first time then the Connection status becomes Untrusted after receiving Stage 0 or 1. But when the same payload is executed twice then a Healthy connection is achieved, why ? How can you expect this behavior on a Red Team Engagement ? Why a victim will click payload two time ?

    7) Finally, The check-in option should be on interactive panel with countdown :- I also requested it 1.5 months ago, but nobody responded link:- https://github.com/cobbr/Covenant/issues/389

It's been 2 years for last update, I think you have taken a good amount of rest Mr. Cobbr, now you should come back to work on your terminal. Because I can't spend my days on modifying covenant personally, and some issues I can't resolve by myself as I am not a "c sharp" coder, as I mentioned earlier.

Thanks,
Waiting for your response.....

[khraoverflow]

Feature Request or Bug Feature Request

**Describe the feature request ** Will there be comparability with the newer versions of Dotnet? It seems like Covenant requires 3.1 dotnet has reached EOL and is unsupported by Windows. Covenant is a great tool, and I would like to not have to do other methods for a C2 server.

i doubt this repo will come back to life ,either way while we wait, i guess we can do our own chores it's open source after all riight ? xD so here's my fork , i just update it to .net 8 : https://github.com/khraoverflow/Covenant
but ofc i didn't test everything so not sure if there's anything broken but it should be fine as far i as i tried now.

[chvancooten]

@alina41c: It's been 2 years for last update, I think you have taken a good amount of rest Mr. Cobbr, now you should come back to work on your terminal.

Bruh... This code has been provided to you for free, the author is in no way obliged to do anything about the problems you are now facing with it. They "should" not do anything. Fix it yourself or find other ways to support the project if you are so dependent on using it in your operations.

@alina41c: It's been 2 years for last update, I think you have taken a good amount of rest Mr. Cobbr, now you should come back to work on your terminal.

Bruh... This code has been provided to you for free, the author is in no way obliged to do anything about the problems you are now facing with it. They "should" not do anything. Fix it yourself or find other ways to support the project if you are so dependent on using it in your operations.

Sorry, if I seem harsh
But you said directly and the honest words that hit!!

Anyway, I shared the issue with my group leader and now we are using Brute Ratel C4 in our operations
Sorry, I can't contribute anything as I am not good in C#

[cobbr]

No offense is taken here, I take it as a compliment that folks are still using the project and wishing for much needed updates. I will point out that the last commit was 10 months ago, not 2 years, (check the dev branch) but that's the only point I'm offended by 🙂

I'd love to get back to Covenant development eventually but I can't promise when that will be. I've just had competing work and life priorities, so I haven't had as much time to work on this project as of late. In the meantime, please feel free to modify or fork as desired within the terms of the GPLv3 license.

I am still personally an active Covenant user and find that the project still works well despite a lack of active development. Dotnet 5 hitting EOL is a real issue for the project, so it may be worth a small update to move to a newer version. But it will be hard to resist a more comprehensive update while doing so and, again, I can't make any promises about providing that within any particular timeframe.