Skip to content
#

packet

Here are 289 public repositories matching this topic...

eltariel
eltariel commented Jan 30, 2022

When you run inletsctl create, it prints a command to run in order to delete the server again. The command generated for an Azure deployment is incomplete and will not run without additional parameters.

Expected Behaviour

  • Run the inletsctl delete command generated by inletsctl create
  • The inlets server is deleted.

Current Behaviour

  • The provided command fails:
$ inle
enhancement good first issue
daniel5151
daniel5151 commented Sep 17, 2020

Overview

#22 added support for register-level read/writes, and introduced a new RegId associated type to the existing Registers trait. This associated type is used to translate raw GDB register ids (i.e: a arch-dependent usize) into a structured human-readable enum identifying the register.

e.g:

/// 32-bit ARM core register identifier.
#[derive(Debug, Clone, Copy)]
pub 
help wanted good first issue API-ergonomics gdbstub_arch
xhdix
xhdix commented Apr 21, 2022

There is a common mistake and that is that users make a lot of mistakes in providing the correct packet.payload. We should cover their mistakes and/or show the appropriate error if possible.

For example, if the hexdump didn't start with '4' (i.e, IPv4 -- currently supported), show an error. Or try Ether(hexdump) instead of IP(hexdump), and see if there is an IP layer, export `packet.pay

enhancement good first issue priority/medium

Improve this page

Add a description, image, and links to the packet topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the packet topic, visit your repo's landing page and select "manage topics."

Learn more