This is a guide on setting up an IPSEC VPN server on CentOS 7 using StrongSwan as the IPsec server and for authentication. It has a detailed explanation with every step. We choose the IPSEC protocol stack because of recent vulnerabilities found in pptpd VPNs and because it is supported on all recent operating systems by default. Why a VPN?More than ever, your freedom and privacy when online is under threat. Governments and ISPs want to control what you can and can't see while keeping a record of everything you do, and even the shady-looking guy lurking around your coffee shop or the airport gate can grab your bank details easier than you may think. A self hosted VPN lets you surf the web the way it was intended: anonymously and without oversight.A VPN (virtual private network) creates a secure, encrypted tunnel through which all of your online data passes back and forth. Any application that requires an internet connection works with this self hosted VPN, including your web browser, e...

Intel AHCI 驱动安装方法及常见问题汇总（20131219）   相关文章 　　·　Win XP系统下开启AHCI硬盘工作模式的方法 　　·　Windows系列系统如何安装硬盘驱动（AHCI） 　　·　Intel 6系芯片组Windows XP AHCI驱动加载方法 　　·　Win XP系统下加载Q77芯片组的AHCI驱动安装指导 　　·　Intel RAID/AHCI 驱动程序 　　·　Intel Q67 RAID/AHCI 驱动程序 知识点分析: 希望安装XP系统并开启硬盘的AHCI模式，在F6安装AHCI驱动后出现蓝屏7B的报错。可以看到下图中可选的选项有很多，蓝屏原因是没有选择正确的AHCI驱动导致。上图可以通过键盘上的“↓”键盘还可以选择更多的选项。操作步骤: 为了方便大家安装，将芯片组及对应驱动的选择进行了汇总，如下：1. Intel 3 Series Chipset，如：Q35选择：Intel(R) ICH9R/DO/DH SATA AHCI Controller2. Intel 4 Series Chipset，如：Q45选择：Intel(R) ICH10D/DO SATA AHCI Controller3. Intel 5 Series Chipset，如：Q57、H55、H57选择...

在安装WIN2003 SERVER时,在启动过程中按F6后,再按S加载RAID卡驱动后,在复制完文件重新启动后无法继续安装 故障描述:配置RAID/SCSI卡的机型，在安装WIN2003 SERVER时，在启动过程中按F6后，再按S加载RAID卡驱动后，按Enter继续安装仍提示找不到硬盘。解决方案:因为win2003server与WIN2000不同，在安装系统时，在按F6后(是英文界面)，需按两次"S"加载RAID卡之类设备的驱动程序：第一次按S键是加载Specify Additional Device软盘驱动;在加载完软盘驱动后，系统提示“The driver you provided seems to be newer than the Windows default driver.”，再下面提示：按“S”继续。 到屏幕上出现“Setup will load support for the following mass storage device(s)...”时，按回车键可以继续安装。而在在默认情况下可能习惯于WIN2000的安装方式，直接按回车加载驱动，按“Enter”是加载WINDOWS系统自带的驱动程序，所以会出现上述情况。

您所在的组无权查看该日志

Virtual Development BoardIf you want to have an Embedded Linux Development Board, and you don't want to pay for it, then you can DIY a Virtual Development Board.The Virtual Development Board is an emulation board which made from QEMU, actually it's a Virtual Machine. Contents1 Debug Mode1.1 QEMU1.1.1 Download QEMU1.1.2 Install QEMU1.2 Bootloader1.2.1 Prepare Cross Toolchain1.2.2 Download U-Boot1.2.3 Cross compile U-Boot1.2.4 Debug U-Boot1.3 Linux Kernel1.3.1 Download Linux Kernel1.3.2 Cross Compile Linux Kernel1.3.3 Load Linux Kernel1.3.3.1 Download and Install Open TFTP Server1.3.3.2 prepare qemu-ifup & qemu-ifdown1.3.3.3 tftpboot uImage1.3.4 run linux kernel1.3.4.1 prepare the rootfs1.3.4.2 prepare the nfs1.3.4.3 run linux kernel1.4 driver1.4.1 add a device to QEMU1.4.2 write the device driver1.5 GUI2 Run Mode2.1 QEMU2.1.1 Support FLASH on QEMU2.1.2 Fix Compilation Errors2.2 U-Boot2.2.1 burn U-Boot into flash3 References4 External linksDebug ModeQEMUDownload QEMUThere are two wa...

Arm64QemuQemu 2.0 includes arm64 support, and Debian 8 (and above) fully supports it. BackgroundIn October 2013 the arm64 (aarch64) qemu port became publicly available. It is a user-space emulation, so it may not be applicable to all development tasks. It is fine for building software, and it is _much_ faster and often easier to use than ARM's proprietary (free beer) Foundation Model. The development was done by folks at SUSE Linux, so kudos to them. This code was incorporated into Qemu 2.0 in March 2014 by Linaro, and there is no longer a need to build arm64 from the development branch. You can verify support by checking for the availability of the aarch64 interpreter: # update-binfmts --display | grep -i aarch qemu-aarch64 (enabled): interpreter = /usr/bin/qemu-aarch64-staticInstallationSince Debian supports arm64, installation is as simple as as the following. Step 1The first task is to elevate to root: $ su - password: #Step 2The second step is to configure locales so your Qem...

Testing QEMU ARM TrustZoneA while back we wrote about the QEMU implementation of ARM TrustZone, also known as ARM Security extensions support, and now that this work is being accepted into mainline QEMU we want to highlight some aspects about the usage model and testing of the functionality.Ongoing Work and ProgressSince the last post, the bulk of the ARM CPU Security Extension support has made it to upstream QEMU. Although the functional support is now available upstream, it is currently disabled while the details of the usage are ironed out. Specifically, command line options are being added to allow users to enable or disable the ARM Security extensions from the command line. This is especially important for maintaining backwards compatibility of existing machine models incorporating TrustZone enabled processors.Achieving backwards compatibility and allowing easy future use of ARM TrustZone, we are introducing the following configuration changes:The Security Extensions will be avai...

ARM® TrustZone® in QEMUEver used an application on your smartphone or tablet that accesses security sensitive information such as banking, personal health information, or credit cards?  The demand for mobile devices to do more and more is rapidly growing and includes increased security sensitive tasks.  At the same time, malicious apps are also flooding mobile app stores in hopes of exploiting security holes to take advantage of unsuspecting users.Can we rely on certain apps to protect our personal data and prevent undesired and unauthorized access?  The current solution is to present users with warning dialogs when downloading applications and otherwise trust the rest of the system.  This does not work for a number of reasons.  First, existing protection and isolation principles may not work.  Second, applications may not be implemented according to secure programming guidelines.  Third, other users of devices (such as children or friends) m...

您所在的组无权查看该日志

确认 PHP 能够正常工作后，编辑 /usr/local/Comsenz/etc/php.ini 进行设置提升 PHP 安全性。查找disable_functions =修改成disable_functions = passthru,exec,system,chroot,scandir,chgrp,chown,escapeshellcmd,escapeshellarg,shell_exec,proc_get_status,ini_alter,ini_alter,ini_restore,dl,pfsockopen,openlog,syslog,readlink,symlink,leak,popepassthru,stream_socket_server,popen然后重启 web 服务：service httpd restart查找disable_functions然后用下面的替换 复制代码 代码如下: disable_functions =phpinfo,exec,passthru,shell_exec,system,proc_open,popen,curl_exec,curl_multi_exec,parse_ini_file,show_source Save and close the file. Restart httpd: 复制代码 代码如下: # service httpd restart Note that the disable_functions directive can not be used outside of the php.ini file which means that you cannot disable functions on a per-virtualhost or per-directory basis in your httpd.conf file. If we add this to our php.ini file: iis中设置方法，在c:\windows\php.ini星外的设置： 代码如下: disable_functions =exec,system,p...