🦑 Fastest way to rebuild the indexes of a Version 8.x or later database:
1)Indexes must be rebuilt after binary loading the data.
2) In Version 9.1, Progress introduced an option to rebuild the index structure during the binary load phase. An offline idxbuild is still faster particularly since additional parameters were introduced in IDXBUILD Utility for Progress 9.1D07 or higher and OpenEdge 10.2B06 or higher
1)Indexes must be rebuilt after binary loading the data.
2) In Version 9.1, Progress introduced an option to rebuild the index structure during the binary load phase. An offline idxbuild is still faster particularly since additional parameters were introduced in IDXBUILD Utility for Progress 9.1D07 or higher and OpenEdge 10.2B06 or higher
Forwarded from Backup Legal Mega
146 - Router Security Configuration Guide [-PUNISHER-].pdf
3 MB
Forwarded from Backup Legal Mega
147 - Sap Basis Security [-PUNISHER-].pdf
667 KB
Forwarded from Backup Legal Mega
161 - Testing Web Security [-PUNISHER-].pdf
2.6 MB
Forwarded from Backup Legal Mega
162 - The Art Of Intrusion [-PUNISHER-].pdf
1.6 MB
Forwarded from Backup Legal Mega
179 - Thn Sep2011 [-PUNISHER-].pdf
6.6 MB
Forwarded from Backup Legal Mega
115_Low_Voltage_Wiring_Security_Fire_Alarm_Systems_PUNISHER_.pdf
6.9 MB
Forwarded from Backup Legal Mega
116 - Magazine 01 Low [-PUNISHER-].pdf
10.9 MB
Forwarded from Backup Legal Mega
129 - New Linux Course Modules [-PUNISHER-].pdf
370 KB
Forwarded from Backup Legal Mega
130_Ninja_Hacking_Unconventional_Penetration_Testing_Tactics_And.pdf
9.9 MB
Forwarded from Backup Legal Mega
131 - No.Starch.Metasploit.Jul.2011 [-PUNISHER-].pdf
6.9 MB
Forwarded from Backup Legal Mega
132_Oracle_10g_Advanced_Security_Administrartors_Guide_Ww_PUNISHER.pdf
3.2 MB
Forwarded from Backup Legal Mega
🦑 nginx cookie validity period guide by undercode
> Every visit is generated in the browser Cookie, so is Cookiethe existence good or bad for the user? To be honest, the existence of this thing does bring a series of problems. It is interesting that almost every site is difficult to leave Cookie. Because Cookieof its seemingly simple use, it is easy to be underestimated. In the recent development process, reviewing the Cookiecode in the application can obtain huge security benefits at almost a small cost. So write this note to deepen your memory.
> Every visit is generated in the browser Cookie, so is Cookiethe existence good or bad for the user? To be honest, the existence of this thing does bring a series of problems. It is interesting that almost every site is difficult to leave Cookie. Because Cookieof its seemingly simple use, it is easy to be underestimated. In the recent development process, reviewing the Cookiecode in the application can obtain huge security benefits at almost a small cost. So write this note to deepen your memory.
Forwarded from Backup Legal Mega
🦑Cookie security risks
1) In the actual application scenario, Cookiethe one thing that is used the most is to maintain the identity authentication server state.
2) This hold may be session- Sessionbased, or it may be persistent. However, no matter which one, once the Cookieserver ticket included in the identity authentication Ticketis leaked, it will be difficult for the server to distinguish whether the user request with this ticket comes from a real user or a malicious ***.
3) In actual cases, the Cookiemost leaked way is through cross-site scripting (such as XSS, Cross Site Script) vulnerabilities.
4) The user can JavaScriptsteal an important identity representing the user's identity through a small piece of code Cookie. Because cross-site scripting vulnerabilities are so common (don't think that simple ones HTML Encodecan avoid being cross-site, cross-site is a very deep knowledge, so that a dedicated term in the industry: cross-site division), almost every Websites are inevitable, so this method is a commonly used method in practice.
5) In fact avoid this problem first secret is to do all possible, give your Cookieadd HttpOnlytags. HttpOnlyThe specific use of is outside the scope here
1) In the actual application scenario, Cookiethe one thing that is used the most is to maintain the identity authentication server state.
2) This hold may be session- Sessionbased, or it may be persistent. However, no matter which one, once the Cookieserver ticket included in the identity authentication Ticketis leaked, it will be difficult for the server to distinguish whether the user request with this ticket comes from a real user or a malicious ***.
3) In actual cases, the Cookiemost leaked way is through cross-site scripting (such as XSS, Cross Site Script) vulnerabilities.
4) The user can JavaScriptsteal an important identity representing the user's identity through a small piece of code Cookie. Because cross-site scripting vulnerabilities are so common (don't think that simple ones HTML Encodecan avoid being cross-site, cross-site is a very deep knowledge, so that a dedicated term in the industry: cross-site division), almost every Websites are inevitable, so this method is a commonly used method in practice.
5) In fact avoid this problem first secret is to do all possible, give your Cookieadd HttpOnlytags. HttpOnlyThe specific use of is outside the scope here