msys2 / msys2/msys2-runtime

Cannot launch when enabling Mandatory ASLR in Windows Security

Open
#327 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
240
Forks
60
Avg merge
2d 3h
Merged PRs (30d)
1

Description

As described in title.

The program was not just working at all, and the installation failed as bash cannot launch properlly. If I just unzip and use the exe file directly it says:


Error: Could not fork child process: Resource temporarily unavailable (-1).
DLL rebasing may be required; see 'rebaseall / rebase --help'.

I am not quite sure whether this issue should be reported here or somewhere else, and I am just a user who has no idea what it means, thus no more information can be provided. Sorry for that.

According to the Microsoft docs,

Address space layout randomization (ASLR) is a computer security technique involved in preventing exploitation of memory corruption vulnerabilities. In order to prevent an attacker from reliably jumping to, for example, a particular exploited function in memory, ASLR randomly arranges the address space positions of key data areas of a process, including the base of the executable and the positions of the stack, heap and libraries.

Personally I think it enhanced security, but perhaps some features like forking a process may not work properlly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified. Start by reproducing the bash launch and installation failure with Mandatory ASLR enabled, then trace the reported fork and DLL-rebasing error through the runtime. Done means establishing the affected component and providing a verified fix or a clearly documented incompatibility.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, c
Domain
operating-systems, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.