forked from secdev/scapy
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add .NET Remoting / .NET Binary Formatter (secdev#4606)
- Loading branch information
Showing
5 changed files
with
1,257 additions
and
196 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
.NET Protocols | ||
============== | ||
|
||
Scapy implements a few .NET specific protocols. Those protocols are a bit uncommon, but it can be useful to try to understand what's sent by .NET applications, or for more offensive purposes (issues with .NET deserialization for instance). | ||
|
||
.NET Remoting | ||
------------- | ||
|
||
Implemented under ``ms_nrtp``, you can load it using:: | ||
|
||
from scapy.layers.ms_nrtp import * | ||
|
||
This supports: | ||
|
||
- The .NET remote protocol: ``NRTP*`` classes | ||
- The .NET Binary Formatter: ``NRBF*`` classes | ||
|
||
For instance you can try to parse a .NET Remoting payload generated using ysoserial with the ``NRBF()`` to analyse what it's doing. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.