microcorruption | my solutions for microcorruption

by draguve Python Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | microcorruption Summary

microcorruption is a Python library. microcorruption has no bugs, it has no vulnerabilities and it has low support. However microcorruption build file is not available. You can download it from GitHub.

my solutions for microcorruption

Support

Quality

Security

License

Reuse

Support

microcorruption has a low active ecosystem.

It has 1 star(s) with 0 fork(s). There are 1 watchers for this library.

It had no major release in the last 6 months.

microcorruption has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of microcorruption is current.

Quality

microcorruption has 0 bugs and 0 code smells.

Security

microcorruption has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

microcorruption code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

microcorruption does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

microcorruption releases are not available. You will need to build from source code and install.

microcorruption has no build file. You will be need to create the build yourself to build the component from source.

It has 122 lines of code, 15 functions and 5 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed microcorruption and discovered the below as its top functions. This is intended to give you an instant insight into microcorruption implemented functionality, and help decide if they suit your requirements.

Hashes the given username .
Force a username to a given bin .
Return a hex representation of a string
Return the endian of an address
Convert a hex string to a string .
Return signed endian representation of an address .
Convert UNIX command to command .
Convert hex to command .
Convert an address to a hex string .

Get all kandi verified functions for this library.

microcorruption Key Features

No Key Features are available at this moment for microcorruption.

microcorruption Examples and Code Snippets

No Code Snippets are available at this moment for microcorruption.

Community Discussions

Trending Discussions on microcorruption

why "add #0x10, sp" adds 16 bits to the sp while "add #0x8, sp" adds only 8? (microcorruption CTF, "cusco" stage)

Negative operand in mov.b Instruction

Why I want to add an address to the stack pointer?

QUESTION

why "add #0x10, sp" adds 16 bits to the sp while "add #0x8, sp" adds only 8? (microcorruption CTF, "cusco" stage)

Asked 2021-Oct-07 at 21:42

in the cusco challenge of microcorruption CTF I noticed that after line 453a the sp adds 16 to the sp value while on line 4476 it adds only 8. why does it happen?

by the way if there are easier challenges you know of to practice my reverse engineering skills i would really appreciate a link thanks!

...

ANSWER

Answered 2021-Oct-07 at 14:15

Hexadecimal. 0x10 is 16; 0x8 is 8.

Source https://stackoverflow.com/questions/69481899

QUESTION

Negative operand in mov.b Instruction

Asked 2020-Dec-22 at 23:14

i am currently working to solve the stage Hanoi in the Microcorruption CTF. This CTF focusses on the MSP430 Family (RISC, 16Bit).

I stumbled across the following lines:

...

ANSWER

Answered 2020-Dec-22 at 23:14

As pointed out in the coments by Peter Cordes, my initial thought is correct. (Even though the wording is off)

The value stored in the memoryaddress, which is equal to the sum of the value stored in r4 plus the offset -4 is decremented by the register plus -4 (offset) and stored in r15. That's it really.

Example:

r4 = 0x43FC and 0x43F8 = 0xAB

The instruction

Source https://stackoverflow.com/questions/65415813

QUESTION

Why I want to add an address to the stack pointer?

Asked 2020-Jan-11 at 00:04

I'm trying to understand the first microcorruption challenge.

I want to ask about the first line of the main function.

Why would they add that address to the stack pointer?

...

ANSWER

Answered 2020-Jan-10 at 21:44

This looks like a 16-bit ISA¹, otherwise the disassembly makes no sense.

0xff9c is -100 in 16-bit 2's complement, so it looks like this is reserving 100 bytes of stack space for main to use. (Stacks grow downward on most machines). It's not an address, just a small offset.

See MSP430 Assembly Stack Pointer Behavior for a detailed example of MSP430 stack layout and usage.

Footnote 1: MSP430 possibly? http://mspgcc.sourceforge.net/manual/x82.html it's a 16-bit ISA with those register names, and those mnemonics, and I think its machine code uses variable-length 2 or 4 byte instructions.

It's definitely not ARM; call and jmp are not ARM mnemonics; that would be bl and b. Also, ARM uses op dst, src1, src2 syntax, while this disassembly uses op src, dst.

Source https://stackoverflow.com/questions/59688685

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install microcorruption

You can download it from GitHub.
You can use microcorruption like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: