seanlion/graph-node-evmos-compatible

Graph Node fork(Evmos compatible)

Hi there 👋

My name is Seung Heo, Ex-Product Manager, Currently Software Engineer.

1. I specialize in backend development and enjoy learning new concepts.
2. My passion lies in mastering new environments, programming languages, and technologies.
3. Currently, I'm focused on system design and writing highly efficient code.

If you are interested in me, Please contact me by email or just chat me. For more details, here is my LinkedIn profile.

---

3년 동안 프로덕트 매니저를 하다, 현재는 소프트웨어 엔지니어로 일하고 있는 허승이라고 합니다.

1. 백엔드 개발을 좋아하고 새로운 개념 배우기를 좋아하는 개발자입니다.
2. 새로운 환경, 프로그래밍 언어, 기술 등을 배우고 익히고 도전하는 환경을 좋아합니다.
3. 요즘은 시스템 설계와 비용 보다 편익이 큰 코드 작성법에 푹 빠져있습니다.

저와 이야기 하고싶은 분들은 언제든지 커피챗☕️ 주세요!

graph-node-evmos-compatible's Issues

RUSTSEC-2022-0075: Bug in pooling instance allocator

Bug in pooling instance allocator

Details
Package	wasmtime
Version	0.27.0
URL	GHSA-wh6w-3828-g9qf
Date	2022-11-10
Patched versions	>=1.0.2, <2.0.0,>=2.0.2

bug in Wasmtime's implementation of its pooling instance allocator where when a linear memory is reused for another instance the initial heap snapshot of the prior instance can be visible, erroneously to the next instance.

Mitigations are described here.

See advisory page for additional details.

RUSTSEC-2022-0076: Bug in Wasmtime implementation of pooling instance allocator

Bug in Wasmtime implementation of pooling instance allocator

Details
Package	wasmtime
Version	0.27.0
URL	GHSA-44mr-8vmm-wjhg
Date	2022-11-10
Patched versions	>=2.0.2

Bug in Wasmtime's implementation of its pooling instance allocator when the allocator is configured to give WebAssembly instances a maximum of zero pages of memory.

In this configuration, the virtual memory mapping for WebAssembly memories did not meet the compiler-required configuration requirements for safely executing WebAssembly modules. Wasmtime's default settings require virtual memory page faults to indicate that wasm reads/writes are out-of-bounds, but the pooling allocator's configuration would not create an appropriate virtual memory mapping for this meaning out of bounds reads/writes can successfully read/write memory unrelated to the wasm sandbox within range of the base address of the memory mapping created by the pooling allocator.

This bug is not applicable with the default settings of the wasmtime crate.

This bug can only be triggered by setting InstanceLimits::memory_pages to zero.

This is expected to be a very rare configuration since this means that wasm modules cannot allocate any pages of linear memory.

All wasm modules produced by all current toolchains are highly likely to use linear memory, so it's expected to be unlikely that this configuration is set to zero by any production embedding of Wasmtime.

See advisory page for additional details.

RUSTSEC-2022-0061: Crate `parity-wasm` deprecated by the author

Crate parity-wasm deprecated by the author

Details
Status	unmaintained
Package	parity-wasm
Version	0.45.0
URL	paritytech/parity-wasm#334
Date	2022-10-01

This PR explicitly deprecates parity-wasm.
The author recommends switching to wasm-tools.

See advisory page for additional details.

RUSTSEC-2021-0139: ansi_term is Unmaintained

ansi_term is Unmaintained

Details
Status	unmaintained
Package	ansi_term
Version	0.12.1
URL	ogham/rust-ansi-term#72
Date	2021-08-18

The maintainer has adviced that this crate is deprecated and will not receive any maintenance.

The crate does not seem to have much dependencies and may or may not be ok to use as-is.

Last release seems to have been three years ago.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

• anstyle
• console
• nu-ansi-term
• owo-colors
• yansi

Dependency Specific Migration(s)

• structopt, clap2

See advisory page for additional details.

RUSTSEC-2020-0095: difference is unmaintained

difference is unmaintained

Details
Status	unmaintained
Package	difference
Version	2.0.0
URL	johannhof/difference.rs#45
Date	2020-12-20

The author of the difference crate is unresponsive.

Maintained alternatives:

• dissimilar

• similar

• treediff

• diffus

See advisory page for additional details.

RUSTSEC-2020-0071: Potential segfault in the time crate

Potential segfault in the time crate

Details
Package	time
Version	0.1.44
URL	time-rs/time#293
Date	2020-11-18
Patched versions	>=0.2.23
Unaffected versions	=0.2.0,=0.2.1,=0.2.2,=0.2.3,=0.2.4,=0.2.5,=0.2.6

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

The affected functions from time 0.2.7 through 0.2.22 are:

• time::UtcOffset::local_offset_at
• time::UtcOffset::try_local_offset_at
• time::UtcOffset::current_local_offset
• time::UtcOffset::try_current_local_offset
• time::OffsetDateTime::now_local
• time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

• at
• at_utc
• now

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

Workarounds

No workarounds are known.

See advisory page for additional details.

RUSTSEC-2020-0016: `net2` crate has been deprecated; use `socket2` instead

net2 crate has been deprecated; use socket2 instead

Details
Status	unmaintained
Package	net2
Version	0.2.37
URL	deprecrated/net2-rs@3350e38
Date	2020-05-01

The net2 crate has been deprecated
and users are encouraged to considered socket2 instead.

See advisory page for additional details.

RUSTSEC-2021-0110: Multiple Vulnerabilities in Wasmtime

Multiple Vulnerabilities in Wasmtime

Details
Package	wasmtime
Version	0.27.0
Date	2021-09-17
Patched versions	>=0.30.0

• Use after free passing externrefs to Wasm in
  Wasmtime

• Out-of-bounds read/write and invalid free with externrefs and GC safepoints
  in
  Wasmtime

• Wrong type for Linker-define functions when used across two
  Engines

See advisory page for additional details.

RUSTSEC-2020-0036: failure is officially deprecated/unmaintained

failure is officially deprecated/unmaintained

Details
Status	unmaintained
Package	failure
Version	0.1.8
URL	rust-lang-deprecated/failure#347
Date	2020-05-02

The failure crate is officially end-of-life: it has been marked as deprecated
by the former maintainer, who has announced that there will be no updates or
maintenance work on it going forward.

The following are some suggested actively developed alternatives to switch to:

• anyhow
• eyre
• fehler
• snafu
• thiserror

See advisory page for additional details.

RUSTSEC-2020-0163: `term_size` is unmaintained; use `terminal_size` instead

term_size is unmaintained; use terminal_size instead

Details
Status	unmaintained
Package	term_size
Version	0.3.2
URL	clap-rs/term_size-rs#31
Date	2020-11-03

The term_size crate is no longer maintained. Consider using
terminal_size instead.

See advisory page for additional details.

RUSTSEC-2020-0168: mach is unmaintained

mach is unmaintained

Details
Status	unmaintained
Package	mach
Version	0.3.2
URL	fitzgen/mach#63
Date	2020-07-14

Last release was almost 4 years ago.

Maintainer(s) seem to be completely unreachable.

Possible Alternative(s)

These may or may not be suitable alternatives and have not been vetted in any way;

• mach2 - direct fork

See advisory page for additional details.