WAS5.1中配置error-page不起作为是什么原因

博客专家认证

2006-08-03 01:54:27

一、error-page中配置了404错误，如下：
<error-page>
<error-code>404</error-code>
<location>/errors/404.jsp</location>
</error-page>
<error-page>
<error-code>500</error-code>
<location>/errors/500.jsp</location>
</error-page>
<error-page>
<exception-type>java.lang.Throwable</exception-type>
<location>/errors/exception.jsp</location>
</error-page>
二、位置正确，在Tomcat5.0和WSAD开发环境中，都起作用。

但是一放到WAS5.1下发布，就不起作为，希望大家给我帮助。

...全文

448 4 打赏收藏转发到动态举报

写回复

4 条回复

切换为时间正序

请发表友善的回复…

发表回复

KimSoft 2006-09-08

打赏
举报

回复

CSDN的高手呢？

KimSoft 2006-08-07

打赏
举报

回复

唉。

plmplmplm 2006-08-03

打赏
举报

回复

命名不规范
可以修改再试
具体msn联系

KimSoft 2006-08-03

打赏
举报

回复

不起作为=不起作用

Core name: Xilinx LogiCORE Serial RapidIO Version: 5.5 Release Date: April 19, 2010 ================================================================================ This document contains the following sections: 1. Introduction 2. New Features 3. Supported Devices 4. Resolved Issues 5. Known Issues 6. Technical Support 7. Other Information (optional) 8. Core Release History 9. Legal Disclaimer ================================================================================ 1. INTRODUCTION For the most recent updates to the IP installation instructions for this core, please go to: http://www.xilinx.com/ipcenter/coregen/ip_update_install_instructions.htm For system requirements: http://www.xilinx.com/ipcenter/coregen/ip_update_system_requirements.htm This file contains release notes for the Xilinx LogiCORE IP Serial RapidIO v5.5 solution. For the latest core updates, see the product page at: http://www.xilinx.com/rapidio/ 2. NEW FEATURES - ISE 12.1 software support - Designed to RapidIO Interconnect Specification v2.1 - Virtex-6 LXT/HXT/SXT 5.0 Gbps support - Spartan-6 3.125 Gbps and 4x support - Expanded simulator support - Support for ML505, ML605 and SP605 boards (see Release Notes AR for details) 3. SUPPORTED DEVICES - Virtex-6 LXT/HXT/SXT/CXT - Spartan-6 LXT - Virtex-5 LXT/FXT/SXT - Virtex-4 FX 4. RESOLVED ISSUES - PHY does not properly pass CRF bit to Buffer - Version fixed : v5.5 - CR# 519603 - Updated PHY to properly pass CRF - GT settings for Spartan-6 and Virtex-6 updated based on characterization - Version fixed : v5.5 - PORT_INITIALIZED toggles indefinitely - Version fixed : v5.5 - CR# 551271 - GT wrappers updated so that the core will detect invalid data until RESETDONE asserts. - Processing Element Features CAR implemented incorrectly - Version fixed : v5.5 - CR# 528369 - Part of the PEF CAR was implemented in the PHY configuration space, now it is merged into the LOGIO configuration space as directed by the spec. See core User Guide for map of configuration space. - Recommended modifications to Example Design reset scheme - Version fixed : v5.5 - CR# 533208, 533209, 533212 - Updated reset sequence, see AR# 33574 for specifics. - Example design "implement.bat" file has error - Version fixed : v5.5 - CR# 533796 - Corrected syntax for NGDBuild command. - Virtex-6 clock modules not using production MMCM settings - Version fixed : v5.4rev1 - CR#546021 - Using outdated values from the clocking wizard in clock modules. - Buffer BRAM using READ_FIRST mode - Version fixed : v5.4rev1 - CR#546424 - Using READ_FIRST mode for buffer BRAMs - need to update to WRITE_FIRST mode for Spartan-6 and Virtex-6 based on characterization. - VHDL example design simulation error when CRF bit de-selected - Version fixed : v5.4rev1 - CR# 532020 - Updated example design so that CRF signals not added when CRF support is disabled. - Virtex-6 bring-up issues - Version fixed : v5.4 - CR#527725, CR#525309, CR#531695 - Using integer values for the MMCM_ADV, regenerated Virtex-6 wrappers based on general hardware characterization results, revised reset sequence. Please see core Release Notes for updates. - GUI settings incorrect or not properly reflected in hardware. - Version fixed : v5.4 - CR#507334, CR#528369, CR#528370 / AR#32122 - The following register fields were corrected: Re-transmit Suppression mask, Logical Layer extended features pointer, DeviceVendorID. - Latches inferred in VHDL example design - Version fixed: v5.2 - CR#509670 / AR#32189 - Added intermediate values for partial register and combinational assignments. - lnk_trdy_n does not assert in evaluation core simulations - Version fixed : v5.1rev1 - CR#493479 / AR#31864 - Modified initial state in evaluation cores. - PHY won't generate stand-alone due to missing module - Version fixed : v5.1rev1 - CR#493162 / AR#31834 - Shared file between buffer and log added to buffer file list. - Virtex-4 core has long initialization time - Version fixed : v5.1rev1 - CR#481684 / AR#31617 - Virtex-4 initSM modified to prevent branch to silent when RX PCS resets in DISCOVERY state. - LogIO local arbitration doesn't account for valid causing re-arbitration prior to legitimatepacket completion. - Version fixed : v5.1 - CR#478748 - Valid used to gate mresp_eof_n and iresp_eof_n for local arbitration. - A ireq_dsc_n asserted for an undefined packet type does not get propogated by the logical layer. - Version fixed : v5.1 - CR#478541 - undefined packet type decode now passes dsc to buffer allowing packet to be dropped. - 16-bit deviceID cores may see a maintenance response transaction presented but not validated on the IResp interface resulting in a lost transaction. by the logical layer. - Version fixed : v5.1 - CR#474894 - Fixed issue when the maintenance response is followed immediatly by a single DWord SWrite packet. - SourceID not configureable for IReq port. - Version fixed : v5.1 - CR#473938 - Added ireq_src_id port to logical layer. All transmit source IDs should now be configureable and all received destination IDs observable. - Write enables into LogIO registers aren't allowing partial register writes. - Version fixed : v5.1 - CR#473441 - Write enables now implementedfor all LogIO registers allowing byte-wise writes of CSRs such as the deviceID register and BAR. - Message response transaction received as a user defined packet type using 16-bit device IDs appears as a corrupted packet on the IResp interface. - Version fixed : v5.1 - CR#473400, CR#473693 - Fixed LogIO RX to properly handle all user-defined types. - PHY core does not dsc upon retry when coincident with TX packet eof resulting in potential buffer lock-up - Version fixed : v4.4rev2 - CR#478246 / AR#31407 - lnk_tdst_dsc_n now asserted for all retry and error scenarios. - Retry of packet being sent causes packet to get stuck in buffer - Version fixed : v4.4rev2 - CR#477217 / AR#31318 - No longer applicable, v5.1 introduces new buffer. - Core accepts muddled packet when reinitializing during packet receipt - Version fixed : v4.4rev1 - CR#477115 / AR#31308 - Core PNAs packet in receipt when link goes down. - Core LCSBA implementation removes 64MB of possible addressing space. - Version fixed : v4.4 - CR#472992 / AR#30939 - Use 10-bit mask with full 34-bit address for LCSBA intercept. - CRC error on stalled packet - Version fixed : v4.4 - CR#469678 / AR#30940 - Fixed condition which loaded in new CRC sequence on a stall just after sof received by PHY. This is a non-concern for Xilinx buffer users. - Virtex-4 4x core may intermittenly train down to 1x mode - Version fixed : v4.4 - CR#467616 / AR#30314 - Modified oplm_pcs_rst_sequence.v file supplied with the core to register asynchronous TXLOCK and RXLOCK signals. - Re-initialization not forced following a change to Port Width Override - Version fixed : v4.4 - CR#459427 / AR#30323 - Modified PHY Layer to detect a change in the port width override field and reinitialize when updated. - Messaging packets providing incorrect treq_byte_count value - Version fixed : v4.4 - CR#467116 / AR#30320 - Modified Logical Layer to properly decode Messaging size field. Modified testbench to properly check byte count for messaging type packets. - 8-bit SWrite transactions usign 16-bit deviceIDs suffer lost eofs - Version fixed : v4.4 - CR#467668 / AR#30322 - Modified Logical Layer to properly forward eof through the pipeline. - Some Logical Layer CARs are not being set correctly in the core. - Version fixed : v4.4 - CR#458414 / AR#30054 - The following Logical Layer CARs are not being set correctly in the core: - Assembly Information CAR (offset 0xC) - ExtendedFeaturesPtr portion - Processing Element Features CAR (offset 0x10) - Switch Port Information CAR (offset 0x14) - Destination Operations CAR (offset 0x1C) - Switch Route Table Destination ID Limit CAR (offset 0x34) - Core does not have functionality to enable the user to drop unintended packets based on Device ID. - Version fixed: v4.3. - CR#455552 - Added a new port called deviceid which indicates the current Device ID value stored in the Base Device ID CSR. - Receive side buffer design may corrupt packets - user may see corrupted packets from the logical layer when many small packets cause the status FIFO to fill. - Version fixed: v4.2 - CR#447884 / AR#29263 - No longer applicable, v5.1 introduces new buffer. - Repeated, transmitted packet accepted control symbols referencing the same AckID cause loss of AckID sync - The user will see this as potentially duplicated received packets which ultimately result in a port error condition. - Version fixed: v4.2 - CR#444561 / AR#29233 - Modified the transmit encoder to send a single packet accepted symbol per back-to-back control symbol. - Stomped packet sent after RFR (Restart-from-Retry)control symbol - The user will occasionally see error recovery on a retry which will affect system bandwidth. - Version fixed: v4.2 - CR#435188 / AR#24837 - Modified the PHY interface to kill a packet if discontinued on eof and prevent entry to the buffer. 5. KNOWN ISSUES The following are known issues for v5.5 of this core at time of release: - NGDBuild errors when using ISE GUI unless XST Keep Hierarchy set to Soft - Version to be fixed : Fix Not Scheduled - CR#534514 / AR#33528 - Please reference the Answer Record for additional information and recommendations. - Virtex-4 FX 3.125G, 4x core may not meet timing. - Version to be fixed : Fix Not Scheduled - CR#506364 / AR#32195 - Please reference the Answer Record for additional information and recommendations. - Unable to traindown to x1 mode in Lane 2. - Version to be fixed : Fix Not Scheduled - CR#457109 / AR#30023 - Traindown in Lane 0 works successfully but the Serial RapidIO endpoint is unable to traindown to Lane 2. The RocketIO transceivers only allow traindown to the channel bonding master. - Core reinitialization during error recovery causes recoverable protocol error. - Version to be fixed : Fix Not Scheduled - CR#457885 / AR#30021 - This is an corner condition that could occur if core is forced to reinitialize (i.e. - force_reinit) while it is in the process of error recovery. If this condition occurs, packets will be sent during recovery's quiet period. This situation is recoverable. - Post-Synplicity synthesis implementation runs may exhibit ucf failures - Version to be fixed : Fix Not Scheduled - CR#447782 / AR#29522 - Synplicity generated net names are not consistent with XST generated names and may not be consistent between core types. The .ucf file must be edited in these failure cases. Please reference the Serial RapidIO v5.1 web Release Notes for suggested work around. - PNA cause field may occasionally reflect a reserved value - Version to be fixed : Fix Not Scheduled - CR#436767 / AR#24982 - The cause field is for debug purposes only and will not affect functionality. Occurrence is rare and requires alignment of multiple control symbols. - Control Symbols may be lost on reinit - Version to be fixed : Fix Not Scheduled - CR#436768 / AR#24970 - This is an unusual and ultimately recoverable error. Set the "Additional Link Request Before Fatal" value on the Physical Configuration page of the GUI to "4" in order to prevent a lost Link Request or Link Response from causing the core to enter the port error state. - Logical Rx does not support core side stalls - Version to be fixed : Fix Not Scheduled - CR#436770 / AR#24968 - The rx buffer must provide packets to the logical layer without buffer induced stall cycles. The buffer reference design provided with the core is a store and forward buffer and complies with this rule. The most recent information, including known issues, workarounds, and resolutions for this version is provided in the IP Release Notes Guide located at www.xilinx.com/support/documentation/user_guides/xtp025.pdf 6. TECHNICAL SUPPORT To obtain technical support, create a WebCase at www.xilinx.com/support. Questions are routed to a team with expertise using this product. Xilinx provides technical support for use of this product when used according to the guidelines described in the core documentation, and cannot guarantee timing, functionality, or support of this product for designs that do not follow specified guidelines. 7. OTHER INFORMATION - N/A 8. CORE RELEASE HISTORY Date By Version Description ================================================================================ 04/2010 Xilinx, Inc. 5.5 5.0 Gbps support 03/2010 Xilinx, Inc. 5.4 Revision 1 11.5 support/Patch Release 09/2009 Xilinx, Inc. 5.4 Spartan-6 support 06/2009 Xilinx, Inc. 5.3 Virtex-6 support 04/2009 Xilinx, Inc. 5.2 11.1i support 11/2008 Xilinx, Inc. 5.1 Revision 1 Patch Release 09/2008 Xilinx, Inc. 5.1 New Buffer LogiCore 07/2008 Xilinx, Inc. 4.4 Revision 2 Patch Release 07/2008 Xilinx, Inc. 4.4 Revision 1 Patch Release 06/2008 Xilinx, Inc. 4.4 Bug Fixes 03/2008 Xilinx, Inc. 4.3 10.1i support 10/2007 Xilinx, Inc. 4.2 9.2i support 02/2007 Xilinx, Inc. 4.1 9.1i support 02/2006 Xilinx, Inc. 3.1 Revision 1 Patch Release 01/2006 Xilinx, Inc. 3.1 8.1i support ================================================================================ 9. Legal Disclaimer (c) Copyright 2006 - 2010 Xilinx, Inc. All rights reserved. This file contains confidential and proprietary information of Xilinx, Inc. and is protected under U.S. and international copyright and other intellectual property laws. DISCLAIMER This disclaimer is not a license and does not grant any rights to the materials distributed herewith. Except as otherwise provided in a valid license issued to you by Xilinx, and to the maximum extent permitted by applicable law: (1) THESE MATERIALS ARE MADE AVAILABLE "AS IS" AND WITH ALL FAULTS, AND XILINX HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, NON- INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE; and (2) Xilinx shall not be liable (whether in contract or tort, including negligence, or under any other theory of liability) for any loss or damage of any kind or nature related to, arising under or in connection with these materials, including for any direct, or any indirect, special, incidental, or consequential loss or damage (including loss of data, profits, goodwill, or any type of loss or damage suffered as a result of any action brought by a third party) even if such damage or loss was reasonably foreseeable or Xilinx had been advised of the possibility of the same. CRITICAL APPLICATIONS Xilinx products are not designed or intended to be fail- safe, or for use in any application requiring fail-safe performance, such as life-support or safety devices or systems, Class III medical devices, nuclear facilities, applications related to the deployment of airbags, or any other applications that could lead to death, personal injury, or severe property or environmental damage (individually and collectively, "Critical Applications"). Customer assumes the sole risk and liability of any use of Xilinx products in Critical Applications, subject only to applicable laws and regulations governing limitations on product liability. THIS COPYRIGHT NOTICE AND DISCLAIMER MUST BE RETAINED AS PART OF THIS FILE AT ALL TIMES.

流光4.71的使用方法,这里有使用说明可以下载自己看一下:http://www.yeshack.com/jc/200508/2345.html 工具这种东西本身就是一把双刃剑，如果因为自己的站点密码太过简单而被攻破然后归罪于因特网上一些免费或共享软件的话，恐怕是有些目光短浅了。管辖的系统存在漏洞而不自知的话，就算没被人‘干掉'，也只是一种暂时的‘虚假安全'。一、小榕流光使用的简单说明要谈流光还真找不着感觉——在小榕的帮助文件里已经把软件的使用方法详尽无比地描述过了（强烈建议使用者使用前将帮助文件多读两遍）——我就说三个方面吧——高手完全可以略过的...... 1、对某FTP主机一次完整的在线安全检测过程 A、选定主机：右键单击FTP主机选项，从弹出菜单中选择添加——将目标的IP地址填入，如"210.142.192.13"...... B、选定用户：右键单击该IP地址，可选添加(将想测试的用户名逐个加入)添加方案(可在方案中编辑希望测试的用户名列表)从列表添加(直接从字典文件中导入)及从SMTP主机导入(导入SMTP主机探测到的用户名)，假设你想探测的用户名为quack,便直接在"添加"中填入quack。 C、选择字典： a、简单模式探测：在选项菜单条中对字典及简单模式设置做适当修正以适应本次测试要求，当然你也可以在面板上的单词小写、简单后缀等按钮直接选定。 b、标准模式探测：在"解码字典或方案"中选定某一字典(方案)。 D、调整设置：检查选项菜单栏中的系统设置、连接选项和探测选项，将本次测试的各种选项调整至最优。 E、开始探测：在"探测"菜单中选定"简单模式"或"标准模式"，开始此次安全检测。 F、注意事项：由于流光的系统占用较高，最好不要再开其它应用程序；在在线检测时可能有时会出现假死机现象，这时你可以通过观察MODEM的RD与SD灯来判断程序是否正常运作。 2、密码字典的选用：在线探测相当耗时，所以一个合适的字典会大大降低你的"检测成本"，流光里的工具菜单栏对生成适合自己使用的字典档是一个相当实用的工具——我个人觉得尤其值得使用的是"方案编辑工具"，它能够在你锁定特定用户检测时发挥较大的作用，具体使用帮助文件中写得非常详细，我就不再多说了 ——当然流光里附带的XKEY也是一个相当不错的字典生成程序。 3、流光其实不仅仅是一个在线安全检测工具——而是一个"工具包"，同时具有以下几个辅助功能 A、探测主机端口 B、探测主机类型 C、FINGER D、扫描POP3、FTP主机 E、验证主机用户而其主要功能是对POP3、FTP、HTTP、PROXY主机进行在线密码安全检测。所以——一句话，功能强大，试过便知。至于同样原理的在线密码破解软件国内流行的也并不少，如很早以前的emailcrack、wwwhack、网络刺客1 以及现在流传很广网络刺客2、Webcrack、Xavior等等，流光在很大程度上集成了这些软件的功能，但这些软件早期的产品也都缺乏IP隐藏或类似功能，而近期的Webcrack以及Xavior则都具备从代理服务器端进行探测的功能，我认为这应该是在线探测的一个方向——安全第一嘛——基于此想法，我对流光在探测中会留下的记录进行试验：对一位网管朋友的WINDOWS2000 Beta3 SERVER 英文版进行了一番测试，对其上已知的帐号进行密码强攻, 经探测得知其FTP端口是开放的,在未预先通知的情况下对其进行攻击，事后打电话询问其记录情况，在EVENT VIEWER里有如下信息：WARNING:The server was unable to logon the Windows NT account 'houxiourong' due to the following error: Logon failure: unknown user name or bad password.The data is the error code. 而甚至他告诉我，当我的攻击进行到一半时，他的主机上就弹出了The System log file is full.的信息提示框——失败的登陆次数太多以至于其默认为512K的记录文件被撑饱了！所以我要奉劝某些心怀叵测的人们——别做坏事...... 二、密码设置的基本常识及工具 1、有关口令的一些统计 A、数目：在UNIX系统里可以建立多于43,000,000,000,000,000个不同的口令，但如果仅仅组合10种主要语言的字典，加上这些字的反向、大写、简单后缀等一些微小变形，仅能产生不到5,000,000个字......加上一些俚语......也不会超出这个数量级。 B、国外某机构在对一个无约束环境的用户口令选择的调查中显示，只有1.4%的用户口令中含有控制符。 2、介绍几个工具 A、CrackLib 简介及应用举例 by JeffreyDong CrackLib 是什么? CrackLib: A ProActive Password Sanity Library By: Alec Muffett Address: alecm@crypto.dircon.co.uk CrackLib是一个可用于类UNIX系统下的函数库, 一般来说, 通常只使用其中的一个函数. :-) 它可以用于编写和passwd有关的程序中, 其基本思想是很简单的, 就是防止用户使用过于简单, 容易被猜测出来或容易被一些工具搜索到的密码. 密码攻击是网络上最为常见的攻击手段. 随着国内计算机用户水平的提高, 有很多人学会了使用工具搜索密码的方法, 由于某些原因, 含有被加密密码的文件会被某些用户获取; 这时, 过于简单的密码就会成为攻击者的突破口. 网上有很多这方面的报道.(我的一个朋友告诉我他曾用一个星期的时间算出了BTA一个管理员的密码. wow! :-P) 通过限制用户使用不安全的密码, 可以提高你的系统的安全性. CrackLib的特点 CrackLib并不是一个可以直接运行使用的程序, 它是一个函数库, 你可以利用其中的函数写自己的程序,或是加入其它程序中, 用来提高安全性. 比如, 你可以重写passwd, 使用户在选择密码时受到限制. CrackLib使用一个字典, 它查找字典以判断所选用密码是否是不安全的密码, 所以你也可以加入其它信息, 使用自己的字典.比如, 加入公司的名称, 实验室墙上的单词等等潜在的不安全密码. CrackLib的使用非常简单, 它可以被应用于很多地方, 只需加入简单的几行源码, 就可以得到非常好的效果. CrackLib的安装 CrackLib可以很容易的在Internet上找到, 我现在使用的版本是2.7, 跑在我的i586/RedHat Linux和i386/Slackware Linux上. 如果你无法找到它的话, 赶紧去补一补如何在Internet 上查找特定的软件吧, 因为这是一项非常重要的基本功. CrackLib好象没有什么文档, 这也是GNU急需加强的地方. 但是它的安装非常简单, 只要按照 README文件中所叙述的就可以了.如果你用的distribution中包含了这个包, 那它说不定已经安装在你的机器上了,如RedHat 5.1等. :-) 需要注意的是, 不同版本中一些文件所处的目录位置不同, 你要先确定它们所处的位置. 比如, 在RedHat 5.1中, 字典是在/usr/lib/中, 文件名为cracklib_dict.*, 而不是README中所举例的/usr/local/lib/pw_dict.* 应用举例这里我举一个很简单的例子, 试图用很短的篇幅来说明用法. char *FascistCheck(char *pw, char *dictpath); 这是CrackLib中最常用的函数. pw是用户选择的密码, 你要去验证它是不是不安全的. dictpath是字典所在路径, 注意, 要把文件名中"."之前的部分加上.以RedHat 5.1为例, 假设你已正确的安装了CrackLib 2.7和FireBird BBS 2.66M. 让我们来看看如何把CrackLib加入BBS中去. :-) 首先, 改写bbs_src目录下的register.c: /* ----------- begin ---------- */ char *msg; /* ----------- end ---------- */ ...... while( 1 ) { getdata(0,0,"请设定您的密码 (Setup Password): ",passbuf,PASSLEN,NOECHO,YEA) ; if( strlen( passbuf ) < 4 || !strcmp( passbuf, newuser.userid ) ) { prints("密码太短或与使用者代号相同, 请重新输入\n") ; continue; } /* ----------- begin ---------- */ if (msg = (char*) FascistCheck(passbuf, CRACKLIBPATH)) { printf("请另选密码! (%s)\n",msg); continue; } /* ----------- end ---------- */ strncpy( newuser.passwd, passbuf, PASSLEN ); getdata(0,0,"请再输入一次你的密码 (Reconfirm Password): ",passbuf,PASSLEN,NOECHO,YEA); if( strncmp( passbuf, newuser.passwd, PASSLEN ) != 0 ) { prints("密码输入错误, 请重新输入密码.\n") ; continue; } passbuf[8] = '\0' ; strncpy( newuser.passwd, genpasswd( passbuf ), PASSLEN ); break; } begin和end注释所夹部分为改动处, 下同. 接着改写bbs_src目录下的userinfo.c: /* ----------- begin ---------- */ char *msg; /* ----------- end ---------- */ ...... getdata(i++,0,"请设定新密码: ",buf,PASSLEN,NOECHO,YEA); if( buf[0] == '\0' ) { prints("\n\n密码设定取消, 继续使用旧密码\n"); fail++; break; } strncpy(genbuf,buf,PASSLEN) ; /* ----------- begin ---------- */ if (msg = (char*) FascistCheck(buf, CRACKLIBPATH)) { printf("\n请另选密码! (%s)\n", msg); prints("\n密码设定取消, 继续使用旧密码\n"); fail++; break; } /* ----------- end ---------- */ getdata(i++,0,"请重新输入新密码: ",buf,PASSLEN,NOECHO,YEA); if(strncmp(buf,genbuf,PASSLEN)) { prints("\n\n新密码确认失败, 无法设定新密码。\n"); fail++; break; } 接着在bbs.h中加入: #ifndef CRACKLIBPATH #define CRACKLIBPATH "/usr/lib/cracklib_dict" #endif 注意这里是字典所处的位置. 最后改动bbs的Makefile: OS_DEF = -DLINUX -DTERMIOS CC = gcc CFLAGS = -O2 /* ----------- begin ---------- */ LIBS = -ltermcap -lbsd -lcrack /* ----------- end ---------- */ 然后make, make install就可以了. :-) 很简单, 不是吗? 注意：本段关于cracklib的说明转载于[网络工作室] B、Proactive Checking 这个程序能在输入口令时进行一系列的口令检查，这会对避免不安全口令出现于你的系统有帮助作用。它与一般的shadow和NIS(也就是yellow page)口令系统共同工作。 C、Shadow 这个程序取代了原来系统的口令保护机制，它将/etc/passwd文件中的口令信息转移到文件/etc/shadow中，还有一些如口令到期机制、允许16字符口令等功能。 D、Passwd+ 这是一个典型的增强型口令系统。三、应有的措施及其基本知识 1、日志文件大多数日志文件都是由系统一行接着一行写入的文本文件。比如sulog会记录用户使用su命令试图进入系统的情况，在sulog文件尾部附加一条信息，以记录su命令是否被成功使用。不同版本的UNIX系统存放日志文件的目录不同，常见目录如下：/usr/adm 早期的UNIX系统/var/adm 较新版本的UNIX系统/var/log 用于Solaris\Linux\BSD等系统中在这些目录或其子目录下，你可以找到下列文件acct 或 pacct 记录每个用户使用过的命令aculog 拨出"猫"的记录lastlog 记录用户最后一次成功登陆时间及最后一次失败登陆时间loginlog 不良登陆记录messages 输出到主控台及由syslog系统服务程序产生的消息sulog su的使用情况 utmp 记录当前登陆的每个有户 utmpx 扩展的utmp wtmp 记录每一次用户登陆和注销的历史信息及系统开关信息 wtmpx 扩展wtmp vold.log 使用外部介质产生的错误 xferlog FTP存取情况 2、定期运行如crack之类的口令破解程序以检查系统中是否存在弱帐户。

帮客户部署一套mysql并导入数据时出现ERROR 1071 (42000): Specified key was too long; max key length is 1536 bytes错误；环境：数据库版本：mysql5.7.28操作系统：centos6.8CREATETABLE`QRTZ_BLOB_TRIGGERS`(->`SCHED_NAME`varchar(12...

如有 index.jsp 页，当出现后服务器端异异常时要转向到 errorPage.jsp，并在 errorPage.jsp 中把对应错误信息显示出来。我们需要在这两个页面分别加上指令 errorPage="errorPage.jsp" 和isErrorPage="true"。 index.jsp 1 2 3 4 5 <

09-01 00:00:03.596 F/patchoat( 391): art/runtime/gc/heap.cc:286] Check failed: non_moving_space_mem_map != nullptr Failed to mmap at expected address, mapped at 0x6c00 0000 instead of 0x73955000 ...

2,633

社区成员

9,566

社区内容

发帖

与我相关

我的任务

社区管理员

加入社区

近7日
近30日
至今

加载中

查看更多榜单

社区公告

暂无公告

试试用AI创作助手写篇文章吧

+ 用AI写文章