Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed Dotnet Typos in Dotnet Cheatsheet #1466

Merged
merged 2 commits into from
Aug 8, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion cheatsheets/Docker_Security_Cheat_Sheet.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Configuring the container to use an unprivileged user is the best way to prevent
docker run -u 4000 alpine
```

2. During build time. Simple add user in Dockerfile and use it. For example:
2. During build time. Simply add user in Dockerfile and use it. For example:

```dockerfile
FROM alpine
Expand Down
4 changes: 2 additions & 2 deletions cheatsheets/DotNet_Security_Cheat_Sheet.md
Original file line number Diff line number Diff line change
Expand Up @@ -817,7 +817,7 @@ What logs to collect and more information about logging can be found in the [Log

.NET Core comes with a LoggerFactory, which is in Microsoft.Extensions.Logging. More information about ILogger can be found [here](https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.logging.ilogger).

How to log all errors from the `Startup.cs`, so that anytime an error is thrown it will be logged:
Here's how to log all errors from the `Startup.cs`, so that anytime an error is thrown it will be logged:

``` csharp
public void Configure(IApplicationBuilder app, IHostingEnvironment env)
Expand Down Expand Up @@ -965,7 +965,7 @@ Malicious users are able to use objects like cookies to insert malicious informa
DO: Prevent Deserialization of Domain Objects

DO: Run the Deserialization Code with Limited Access Permissions
If a deserialized hostile object tries to initiate a system processes or access a resource within the server or the host's OS, it will be denied access and a permission flag will be raised so that a system administrator is made aware of any anomalous activity on the server.
If a deserialized hostile object tries to initiate a system process or access a resource within the server or the host's OS, it will be denied access and a permission flag will be raised so that a system administrator is made aware of any anomalous activity on the server.

More information about Insecure Deserialization can be found in the [Deserialization Cheat Sheet](Deserialization_Cheat_Sheet.md#net-csharp).

Expand Down
Loading