Forwarded from Backup Legal Mega
π¦How cookies work ?
When you visit the website for the first time, the browser sends a request, and after the server responds to the request, it will be Cookieput into the response request. When the browser sends the request for the second time, it will be Cookietaken over, and the server will identify the user, Of course, the server can also modify the Cookiecontent.
When you visit the website for the first time, the browser sends a request, and after the server responds to the request, it will be Cookieput into the response request. When the browser sends the request for the second time, it will be Cookietaken over, and the server will identify the user, Of course, the server can also modify the Cookiecontent.
Forwarded from Backup Legal Mega
π¦Cookie life cycle :
When it is created Cookie, it will be Cookieassigned a value:, Expireit is the specified Cookievalidity period, that is Cookie, the life cycle, beyond the set life cycle, Cookieit will be cleared. If this value is Expireset to a 0negative value, then this setting will be cleared when the browser is closed Cookie, which is more secure.
When it is created Cookie, it will be Cookieassigned a value:, Expireit is the specified Cookievalidity period, that is Cookie, the life cycle, beyond the set life cycle, Cookieit will be cleared. If this value is Expireset to a 0negative value, then this setting will be cleared when the browser is closed Cookie, which is more secure.
Forwarded from Backup Legal Mega
π¦Modify cookie validity
1) Under normal circumstances, our webapplication services will nginxbe published, at this time, we can nginxchange cookiethe validity period by modifying the configuration file above , because the author is recently based openrestyon the nginxfunction development. Just take this opportunity to start Cookiethe status test of the validity period.
2) As Cookiementioned above in the life cycle, we can Cookieset a reasonable validity period for the safety of the validity period. If 0yes or negative, what is the effect? May wish to take a look
π¦Modify ideas
1) The Use Openrestyof resty.cookieModified. At The Library Used to IS OpenRestyat The HTTP cookieOperation. Of Can BE Used for Nginxparsing HTTP Cookie headerand returning Cookiethe each Field, in. SUCH AS Setting name, value, httponlyand the Properties OTHER
2) Valid for 24h
Here will be expiresset to the validity period is one day (24h), that is, the current system time (ngx.time())plus 24h
1) Under normal circumstances, our webapplication services will nginxbe published, at this time, we can nginxchange cookiethe validity period by modifying the configuration file above , because the author is recently based openrestyon the nginxfunction development. Just take this opportunity to start Cookiethe status test of the validity period.
2) As Cookiementioned above in the life cycle, we can Cookieset a reasonable validity period for the safety of the validity period. If 0yes or negative, what is the effect? May wish to take a look
π¦Modify ideas
1) The Use Openrestyof resty.cookieModified. At The Library Used to IS OpenRestyat The HTTP cookieOperation. Of Can BE Used for Nginxparsing HTTP Cookie headerand returning Cookiethe each Field, in. SUCH AS Setting name, value, httponlyand the Properties OTHER
2) Valid for 24h
Here will be expiresset to the validity period is one day (24h), that is, the current system time (ngx.time())plus 24h
Forwarded from Backup Legal Mega
1) Here we can see that our cookieeffective time is 14:04 on May 13th, indicating that our modified configuration is valid, and can be Cookiemodified through this parameter . As long as this time point is reached, it Cookiewill be invalid and the user You need to log in again.
π¦Validity period is Genesis
2) Here will be expiresset to the validity period is -1, you can observe that the cookie is used in 1970, which is the meta time of the UNIX era
local cookie = resty_cookie:new()
local ok, err = cookie:set({
key = "middle_session",
value = session,
path = "/",
secure = false,
httponly = true,
expires = ngx.cookie_time(-1),
domain = ngx.host,
})
π¦Validity period is Genesis
2) Here will be expiresset to the validity period is -1, you can observe that the cookie is used in 1970, which is the meta time of the UNIX era
local cookie = resty_cookie:new()
local ok, err = cookie:set({
key = "middle_session",
value = session,
path = "/",
secure = false,
httponly = true,
expires = ngx.cookie_time(-1),
domain = ngx.host,
})
Forwarded from Backup Legal Mega
π¦As you can see from the picture below, the Cookievalidity period is January 1, 1970. At this point in time, there is no suspense that is outdated. Of course, it is configured in a production environment. It is to be locked in a small black room to discuss the value of life. Users who encounter such a Cookieconfiguration cannot log in successfully anyway.
Forwarded from Backup Legal Mega
π¦The validity period is current :
Because it ngx.cookie_timewill return a formatted string that can be used as the Cookieexpiration time, we manually specify the expiration time. Through this method, you can test Cookiethe effect of the automatic removal mentioned above
local cookie = resty_cookie:new()
local ok, err = cookie:set({
key = "middle_session",
value = session,
path = "/",
secure = false,
httponly = true,
expires = -1,
domain = ngx.host,
})
Because it ngx.cookie_timewill return a formatted string that can be used as the Cookieexpiration time, we manually specify the expiration time. Through this method, you can test Cookiethe effect of the automatic removal mentioned above
local cookie = resty_cookie:new()
local ok, err = cookie:set({
key = "middle_session",
value = session,
path = "/",
secure = false,
httponly = true,
expires = -1,
domain = ngx.host,
})
Forwarded from Backup Legal Mega
π¦Specify expiration time to 0
local cookie = resty_cookie:new()
local ok, err = cookie:set({
key = "middle_session",
value = session,
path = "/",
secure = false,
httponly = true,
expires = 0,
domain = ngx.host,
})
π¦in conclusion
Here configuration -1, 0in a real sense with hives time is the same, but the benefits of that dark room without closing it. CookieOnly valid on the current page, once you close the browser, this Cookiewill be cleared by the browser, no longer need to consider security issues, support & share us t.me/UndercodeTesting
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
local cookie = resty_cookie:new()
local ok, err = cookie:set({
key = "middle_session",
value = session,
path = "/",
secure = false,
httponly = true,
expires = 0,
domain = ngx.host,
})
π¦in conclusion
Here configuration -1, 0in a real sense with hives time is the same, but the benefits of that dark room without closing it. CookieOnly valid on the current page, once you close the browser, this Cookiewill be cleared by the browser, no longer need to consider security issues, support & share us t.me/UndercodeTesting
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
Forwarded from Backup Legal Mega
Pastebin
VERIFIED PREMIUM NORDVPN - Pastebin.com
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
π¦2020 new phishing tool > Advanced Phishing tool for Linux & Termux
t.me/UndercodeTesting
A) install in one command :
apt update ; apt install git -y ; git clone git://github.com/htr-tech/nexphisher.git ; cd nβ β β ο½ππ»βΊπ«Δπ¬πβ β β β
exphisher ; bash setup ; bash nexphisher
B) apt update
> apt install git -y
>git clone git://github.com/htr-tech/nexphisher.git
> cd nexphisher
> SETUP : bash setup
> SETUP [TERMUX] : bash tmux_setup
> Run : bash nexphisher
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
π¦2020 new phishing tool > Advanced Phishing tool for Linux & Termux
t.me/UndercodeTesting
A) install in one command :
apt update ; apt install git -y ; git clone git://github.com/htr-tech/nexphisher.git ; cd nβ β β ο½ππ»βΊπ«Δπ¬πβ β β β
exphisher ; bash setup ; bash nexphisher
B) apt update
> apt install git -y
>git clone git://github.com/htr-tech/nexphisher.git
> cd nexphisher
> SETUP : bash setup
> SETUP [TERMUX] : bash tmux_setup
> Run : bash nexphisher
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
π¦OWASP Joomla Vulnerability Scanner Project updated in 2019
π¦WHY OWASP JOOMSCAN ?
Automated ...
*Version enumerator
*Vulnerability enumerator (based on version)
*Components enumerator (1209 most popular by default)
*Components vulnerability enumerator (based on version)(+1030 exploit)
*Firewall detector
*Reporting to Text & HTML output
*Finding common log files
*Finding common backup files
π¦πβπππΈπππππΈπππβ & βπβ :
1) git clone https://github.com/rezasp/joomscan.git
2) cd joomscan
3) perl joomscan.pl
π¦For Docker installation and usage
# Build the docker image
docker build -t rezasp/joomscan .
# Run a new docker container with reports directory mounted at the host
docker run -it -v /path/to/reports:/home/joomscan/reports --name joomscan_cli rezasp/joomscan
# For accessing the docker container you can run the following command
docker run -it -v /path/to/reports:/home/joomscan/reports --name joomscan_cli --entrypoint /bin/bash rezasp/joomscan
β verified by Undercode
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
π¦OWASP Joomla Vulnerability Scanner Project updated in 2019
π¦WHY OWASP JOOMSCAN ?
Automated ...
*Version enumerator
*Vulnerability enumerator (based on version)
*Components enumerator (1209 most popular by default)
*Components vulnerability enumerator (based on version)(+1030 exploit)
*Firewall detector
*Reporting to Text & HTML output
*Finding common log files
*Finding common backup files
π¦πβπππΈπππππΈπππβ & βπβ :
1) git clone https://github.com/rezasp/joomscan.git
2) cd joomscan
3) perl joomscan.pl
π¦For Docker installation and usage
# Build the docker image
docker build -t rezasp/joomscan .
# Run a new docker container with reports directory mounted at the host
docker run -it -v /path/to/reports:/home/joomscan/reports --name joomscan_cli rezasp/joomscan
# For accessing the docker container you can run the following command
docker run -it -v /path/to/reports:/home/joomscan/reports --name joomscan_cli --entrypoint /bin/bash rezasp/joomscan
β verified by Undercode
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
GitHub
GitHub - OWASP/joomscan: OWASP Joomla Vulnerability Scanner Project https://www.secologist.com/
OWASP Joomla Vulnerability Scanner Project https://www.secologist.com/ - OWASP/joomscan
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
π¦pro users Analysis of the difference between the units px, rem, em, vh, vw in CSS
1) Absolute length
px
px is the pixel value, is a fixed length, such as our meters, centimeters.
2) Relative length
π¦Why do we need relative length rem em etc?
The fixed length can no longer meet our current needs.
Example: For example, when we shrink our screen, we not only need to reduce the width and height of our box, we also want to reduce our font size, so that the user experience will be better.
rem
π¦The calculation relationship between rem and px
The value of rem is a multiple of px
By default font-size = 16px, then 1rem = 16px
rem how to modify the relative calculation relationship with px
We can modify the font-size: 32px in and only in the html tag (because the html node is the root node, which is r: root in rem), so 1rem = 32px
Code
<div class="div-rem">rem</div>
/* remηη¨ζ³ */
html{
font-size:16px; // 1rem = 16px
}
.div-rem{
width: 10rem; // 10rem = 10 x 16 = 160px
height: 10rem; // 10rem = 10 x 16 = 160px
font-size: 1rem; // 1rem = 16px
background-color: #a58778;
}
in
π¦The calculation relationship between em and px
The value of em is a multiple of px
By default font-size = 16px, then 1em = 16px
em how to modify the relative calculation relationship with px
We can modify the font-size: 32px on our own elements, so that 1em = 32px
If the font-size is not set on our own element, we can also set the font-size on the parent element to affect the em value used by our own element (child element).
The difference between rem and em
written by undercoder
β β β ο½ππ»βΊπ«Δπ¬πβ β β β
π¦pro users Analysis of the difference between the units px, rem, em, vh, vw in CSS
1) Absolute length
px
px is the pixel value, is a fixed length, such as our meters, centimeters.
2) Relative length
π¦Why do we need relative length rem em etc?
The fixed length can no longer meet our current needs.
Example: For example, when we shrink our screen, we not only need to reduce the width and height of our box, we also want to reduce our font size, so that the user experience will be better.
rem
π¦The calculation relationship between rem and px
The value of rem is a multiple of px
By default font-size = 16px, then 1rem = 16px
rem how to modify the relative calculation relationship with px
We can modify the font-size: 32px in and only in the html tag (because the html node is the root node, which is r: root in rem), so 1rem = 32px
Code
<div class="div-rem">rem</div>
/* remηη¨ζ³ */
html{
font-size:16px; // 1rem = 16px
}
.div-rem{
width: 10rem; // 10rem = 10 x 16 = 160px
height: 10rem; // 10rem = 10 x 16 = 160px
font-size: 1rem; // 1rem = 16px
background-color: #a58778;
}
in
π¦The calculation relationship between em and px
The value of em is a multiple of px
By default font-size = 16px, then 1em = 16px
em how to modify the relative calculation relationship with px
We can modify the font-size: 32px on our own elements, so that 1em = 32px
If the font-size is not set on our own element, we can also set the font-size on the parent element to affect the em value used by our own element (child element).
The difference between rem and em
written by undercoder
β β β ο½ππ»βΊπ«Δπ¬πβ β β β