initial commit

README.md

@@ -1,2 +1,127 @@
 # docs
 Repo to hold important notes, links and guides to help throughout the carrer
+
+# GENERAL RESEARCH
+
+## .NET FORMS AUTHENTICATION & SESSION
+### Forms Authentication cookie and Ticket 
+https://support.microsoft.com/en-ca/help/910443/understanding-the-forms-authentication-ticket-and-cookie
+
+### FormsAuthentication cookieless
+With cookieless forms authentication, if the browser is closed, the ticket is lost and a new ticket will be generated on the next request. - https://docs.microsoft.com/en-us/dotnet/api/system.web.configuration.formsauthenticationconfiguration.cookieless?redirectedfrom=MSDN&view=netframework-4.8#System_Web_Configuration_FormsAuthenticationConfiguration_Cookieless
+
+### Forms Authentication Ticket class
+IsPersistent = true if a durable cookie (a cookie that is saved across browser sessions) was issued; otherwise, false. - https://docs.microsoft.com/en-us/dotnet/api/system.web.security.formsauthenticationticket?redirectedfrom=MSDN&view=netframework-4.8
+
+### SAME SITE COOKIE 
+https://web.dev/samesite-cookies-explained/
+
+### Types of cookies
+- There are two different types of cookies - session cookies and persistent cookies. If a cookie does not contain an expiration date, it is considered a session cookie. Session cookies are stored in memory and never written to disk. When the browser closes, the cookie is permanently lost from this point on. If the cookie contains an expiration date, it is considered a persistent cookie. On the date specified in the expiration, the cookie will be removed from the disk. - https://www.cisco.com/c/en/us/support/docs/security/web-security-appliance/117925-technote-csc-00.html#:~:text=If%20a%20cookie%20does%20not,is%20considered%20a%20persistent%20cookie.
+
+### SameSite=Lax not possible for NET < 4.7.2
+Strict (http header) https://docs.microsoft.com/en-us/aspnet/samesite/system-web-samesite#net-versions-earlier-than-472
+
+### SESSION STATE https://docs.microsoft.com/en-us/dotnet/api/system.web.sessionstate.httpsessionstate?view=netframework-4.8#remarks
+- ASP.NET provides session-state management to enable you to store information associated with a unique browser session across multiple requests.
+- Session data is associated with a specific browser session using a unique identifier. By default, this identifier is stored in a non-expiring session cookie in the browser
+- Sessions are started during the first request and session values will persist as long as a new request is made by the browser before the number of minutes specified in the Timeout property pass
+- Session state does not persist across ASP.NET application boundaries. If a browser navigates to another application, the session information is not available to the new application.
+- Session values are stored in memory on the Web server, by default. [..]
+
+### SESSION ABADON https://docs.microsoft.com/en-us/dotnet/api/system.web.sessionstate.httpsessionstate.abandon?view=netframework-4.8#remarks
+- Session identifiers for abandoned or expired sessions are recycled by default. 
+- That is, if a request is made that includes the session identifier for an expired or abandoned session, a new session is started using the same session identifier. You can disable this by setting regenerateExpiredSessionId attribute of the sessionState configuration element to true.
+### SESSION ID https://docs.microsoft.com/en-us/dotnet/api/system.web.sessionstate.httpsessionstate.sessionid?view=netframework-4.8#remarks
+- The SessionID property is used to uniquely identify a browser with session data on the server. 
+The SessionID value is randomly generated by ASP.NET and stored in a non-expiring session cookie in 
+the browser. The SessionID value is then sent in a cookie with each request to the ASP.NET application.
+- The SessionID is sent between the server and the browser in clear text, either in a cookie or in the URL. 
+As a result, an unwanted source could gain access to the session of another user by obtaining the SessionID
+value and including it in requests to the server. If you are storing private or sensitive information in session 
+state, it is recommended that you use SSL to encrypt any communication between the browser and server 
+that includes the SessionID.
+- When using cookie-based session state, ASP.NET does not allocate storage for session data until the Session object is used. 
+As a result, a new session ID is generated for each page request until the session object is accessed. If your
+application requires a static session ID for the entire session, you can either implement the Session_Start method 
+in the application's Global.asax file and store data in the Session object to fix the session ID, 
+or you can use code in another part of your application to explicitly store data in the Session object.
+
+# JSON Web Encryption (JWE)   
+https://tools.ietf.org/html/rfc7516#page-15
+https://openid.net/specs/draft-jones-json-web-encryption-02.html
+
+# GIT
+-- empty commit
+```
+git commit --allow-empty -m "Commit with empty content" && git push
+```
+
+# DOCKER
+```
+docker build -t image . --no-cache
+docker container run -e ENV_VAR="value" --rm -p 3001:80 --name container_name image_name:latest
+docker container exec -it [container] "/bin/bash"
+```
+
+## RUN A SPECIFIC STEP ON DOCKER
+```
+docker build -t image-tag:test --target=test . 
+docker run image-tag:test
+docker build -t temp-test:test --target=test . & docker run temp-test:test
+```
+
+## REDIS
+```
+docker run --name my-redis -d redis redis-server --appendonly yes
+docker container run -p 6379:6379 redis -d
+docker container exec -it my-redis "/bin/bash"
+redis-cli
+127.0.0.1:6379> set farhad likes:stackoverflow
+OK
+127.0.0.1:6379> get farhad
+"likes:stackoverflow"
+```
+
+## MiB Mebibyte 
+one mebibyte is equal to 1048576 bytes
+512 MiB = 536,870,912 bytes
+
+
+# ENTITY FRAMEWORK MIGRATIONS 
+```
+add-migration MIGRATION_NAME	>> adds a new migratin
+dotnet ef migrations add MIGRATION_NAME -o OUTPUT_PATH -c DB_CONTEXT_NAMESPACE
+
+remove-migration	>> remove the latest migration
+
+update-database	>> updates the current database with the latest migration version on the project selected
+update-database MIGRATION_NAME >> rollback/upgrade current database with this migration version
+
+dotnet ef migrations script <FROM> <TO> -o OUTPUT_FILE_PATH -c CONTEXT
+```
+
+# CERTIFICATES
+```
+openssl genrsa -out privatekey.pem 1024 --SHA-1
+openssl genrsa -out privatekey.pem 2048   --SHA-256
+openssl req -new -x509 -key privatekey.pem -out publickey.cer -days 10000
+openssl pkcs12 -export -out public_privatekey.pfx -inkey privatekey.pem -in publickey.cer
+```
+
+# GET HEX (Powershell)
+```
+$ Format-Hex .\pfx\publickey.cer
+```
+
+# INSERT BLOB MYSQL
+```
+SELECT UNHEX('HEX STRING');
+```
+
+# Encode bytes
+```
+$FilePath = "c:\setup\foo.exe"
+$File = [System.IO.File]::ReadAllBytes($FilePath);
+$Base64String = [System.Convert]::ToBase64String($File);
+ ```