設(shè)計(jì)開(kāi)題報(bào)告計(jì)算

LAMPLAMP1.11.1.2.（2）2.2LAMPLAMPLinuxApacheMySQLPHP四個(gè)開(kāi)源軟件構(gòu)成的開(kāi)放資源2.2LAMPLAMPLinuxApacheMySQLPHP四個(gè)開(kāi)源軟件構(gòu)成的開(kāi)放資源Apache服務(wù)器，令其辨識(shí)不同的主機(jī)名。2.2.3Linux2.3LAMP（Linux+Apache+Mysql+Php）1．a(chǎn)ddingthe2．checktherevisetheDeletetheLinuxApache網(wǎng)絡(luò)服務(wù)器，MysqlPHPLinuxApache網(wǎng)絡(luò)服務(wù)器，MysqlPHPLAMP設(shè)計(jì)（論文）起止時(shí)間：201491920155301571112910121314（包括國(guó)內(nèi)外現(xiàn)狀、研究方向、進(jìn)展情況、存在問(wèn)題、參考依據(jù)等（包括國(guó)內(nèi)外現(xiàn)狀、研究方向、進(jìn)展情況、存在問(wèn)題、參考依據(jù)等1.1.發(fā)。ASPASP務(wù)器、MySQLPHPWeb應(yīng)用程掌握”特性，使得它的網(wǎng)絡(luò)開(kāi)發(fā)更加有效[7]。LAMPLAMP得更加具有競(jìng)爭(zhēng)力，更加能吸引客戶。開(kāi)放源代碼的LAMP使用高性能的操作系統(tǒng)Linux)、高性能的網(wǎng)頁(yè)服務(wù)器Apache)、高性能的數(shù)據(jù)庫(kù)(MySQL)、高效率的編程語(yǔ)言(PHP)WebLAMPLinuxWindowsUnix具有先天的優(yōu)勢(shì)。一方面是LinuxLinux對(duì)硬件的要求較低，跨Windows網(wǎng)絡(luò)系統(tǒng)相比，Linux系統(tǒng)的網(wǎng)絡(luò)性能優(yōu)異，具有較好的穩(wěn)定性、高效性和安全性。Linux處在最底層，提供操作系統(tǒng)。靈活性和可定制化的特點(diǎn)使它能夠產(chǎn)生一種高度定制的平臺(tái)，讓其它組件在上面運(yùn)行。Apache，PHPMySQLWindows（IISwebApache）上[8]。LinuxLAMP組合的基礎(chǔ)，它的安全關(guān)系到整個(gè)系統(tǒng)的穩(wěn)定，只有保證LinuxUnixWindows、ApacheApache節(jié)點(diǎn)數(shù)Apache等其他服務(wù)器集成在一起。MySQL體積小，速PHP(HypertextPreprocessor，超文本預(yù)處理器的縮寫)是一種當(dāng)今最為流行的有開(kāi)源和免費(fèi)的獨(dú)特優(yōu)勢(shì)[11]。PHPWebPHPHTMLPHPLinux+Apache+Mysql+Perl/PHP/PythonLinuxApacheWEB服務(wù)器、MySQLPHPhttp請(qǐng)求，都由LinuxApache服務(wù)器處理，如果請(qǐng)求靜態(tài)頁(yè)面，則將目錄下存放PHPPHPPHP面返回給客戶端[12]Internet的快速發(fā)展，電子商務(wù)的普及，網(wǎng)上購(gòu)物已經(jīng)成為一種很普遍的早期安裝一個(gè)LAMP系統(tǒng)是比較復(fù)雜的，隨著面返回給客戶端[12]Internet的快速發(fā)展，電子商務(wù)的普及，網(wǎng)上購(gòu)物已經(jīng)成為一種很普遍的早期安裝一個(gè)LAMP系統(tǒng)是比較復(fù)雜的，隨著Linux的普及現(xiàn)在安裝一個(gè)LAMPLinux發(fā)行版本（Redhat、Debian）安裝時(shí)可Apache、php、mysql等組件。LAMP（Linux、Apache、MySQLPHP/Perl）架構(gòu)的應(yīng)用程序不斷被強(qiáng)大而簡(jiǎn)單的環(huán)境[13]。按照簡(jiǎn)單的形式，基于LAMP的應(yīng)用程序是用PHP這LinuxApacheWebPHPURL戶機(jī)獲得信息，從而確定應(yīng)該執(zhí)行什么操作。PHPApache的一個(gè)擴(kuò)展模塊進(jìn)行安裝的，它不能獨(dú)立運(yùn)行，必須依托于Apache服務(wù)器[14]。服務(wù)器會(huì)從MySQLHTML模板組合在一起，并將結(jié)果返回在內(nèi)的大部分?jǐn)?shù)據(jù)庫(kù)[15]＋PHP＋MySQLLinuxMYSQLLinuxMYSQL數(shù)據(jù)庫(kù)，最后安裝PHPApache。PHPPHPPHPMySQL數(shù)據(jù)PHP語(yǔ)句時(shí)要注意的格式和語(yǔ)法。虞萍.虞萍.影響企業(yè)電子商務(wù)成功的網(wǎng)站因素研究[D].北京中國(guó)農(nóng)業(yè)大張慶壞.我國(guó)同城電子商務(wù)的發(fā)展機(jī)遇及前景[J].吉林工程技術(shù)師范學(xué)院齊晶.中國(guó)電子商務(wù)發(fā)展與規(guī)制研究[D].遼寧:遼寧大學(xué)鄭鎮(zhèn)耿.LAMP環(huán)境架設(shè)Apache虛擬主機(jī)站點(diǎn)[J].計(jì)算機(jī)光盤軟件與應(yīng)彭俊.LAMP的網(wǎng)址導(dǎo)航站的設(shè)計(jì)與實(shí)現(xiàn)[D].南昌:南昌大學(xué)王麗娜.基于LAMP的家樂(lè)電器網(wǎng)上商城的開(kāi)發(fā)[D].大連:大連理工大薛鴻民.基于LAMP的售書網(wǎng)站的設(shè)計(jì)與實(shí)現(xiàn)[J].科技資訊Ramana,U.V.,Prabhakar,T.V.SomeExperimentswiththePerformanceofLAMPArchitecture[C].ComputerandInformationTechnology,2005.CIT2005.TheFifthInternationalConference,2005,P916–920.黃陽(yáng).LAMP架構(gòu)電商平臺(tái)方案設(shè)計(jì)[J].電子商務(wù).2013,10:44-何杭鋒.基于LAMP平臺(tái)的WEB服務(wù)器架構(gòu)[J].中國(guó)新技術(shù)新產(chǎn)ZaidmanA,DemeyerS.Automaticidentificationofkeyclassesinasoftwaresystemusingwebminingtechniques[J].ResearchandPractice.2008,20(6):387–417.張麥玲,王鴻銘.LAMPWEB服務(wù)器安全架構(gòu)[J].數(shù)字技術(shù)與應(yīng)蔣方純.LAMP開(kāi)源軟件編程模式的配置與實(shí)現(xiàn)[J].深圳信息職業(yè)技術(shù)學(xué)肖萍.LAMP平臺(tái)的網(wǎng)站構(gòu)建與分析[J].信息網(wǎng)絡(luò)安全谷和啟.PHP+LINUX+APACHEAttaining原稿題目PerspectivesAttaining原稿題目PerspectivesonFreeand（野生轉(zhuǎn)移，并發(fā)缺陷和分布式系統(tǒng)故障（野生轉(zhuǎn)移，并發(fā)缺陷和分布式系統(tǒng)故障率的編程可以顛覆這些工具的目的,進(jìn)一步比較平衡的討論，請(qǐng)參見(jiàn)五篇論文(Lipner2000;McGraw2000;Neumann2000;Schneider2000;andWittenetal.2000)LeeBadge組織和主持。這些貢獻(xiàn)基本上都是健全這里列出的優(yōu)點(diǎn)或缺點(diǎn)。Lipner探索了一些真正的好處和一些重大缺openish商業(yè)模式。Witten論文探討經(jīng)濟(jì)學(xué)、指標(biāo)和模型。此外，NeumannNeumann2004DARPA的報(bào)告(Neumann2003年)ACM的檔案風(fēng)險(xiǎn)指數(shù)(Neumann2003b)ACM的檔案風(fēng)險(xiǎn)指數(shù)(Neumann2003b)戶和專家可以使他們仔細(xì)研讀代碼并發(fā)現(xiàn)弱點(diǎn)（Kerckhoffs1883年（2002Brown（Collar-Kotelly2002年還有一個(gè)相關(guān)的問(wèn)題就是：有關(guān)被發(fā)現(xiàn)的漏洞信息是否需要公布。20032Slashdot的技術(shù)報(bào)告下載Anderson的重要途徑，并且它經(jīng)常的情況是，開(kāi)放系統(tǒng)（或封閉的系統(tǒng)）PerspectivesonFreeandOpenSource“IsPerspectivesonFreeandOpenSource“Isopensourcesoftwareinherentlybetterthanclosed-sourceproprietarysoftware?”Thisisaquestionthatisfrequentlyheard,withvariousintendedmeaningsof“better.”Asaparticularlydemandingcase,letusconsidercriticalapplicationswithstringentrequirementsforcertainattributessuchassecurity,reliability,faulttolerance,humansafety,andsurvivability,allinthefaceofawiderangeofrealisticadversities—including coordinatedattacks,andactsofGod.Inaddition,let’stossinoperationalrequirementsforextensiveinteroperability,evolvability,maintainability,andcleaninterfacedesignofthosesystems,whilestillsatisfyingthecriticalrequirements.Inthiscontext,weareinterestedindeveloping,operating,andusingcomputersystemsthatarerobustandeasilyTocuttothechase,theanswertothesimplequestionposedinthefirstsentenceissimpleinconcept,butdecidedlynotsosimpleinexecution:Opensourcesoftwareisnotintrinsicallybetterthanclosed-sourceproprietarysoftware.However,ithasthepotentialforbeingbetterifitsdevelopmentprocessaddressesmanyfactorsthatarenormallyexperiencedinmass-marketproprietarysoftware,suchastheWell-definedandthoroughlyevaluatedrequirementsforsystemandapplicationbehavior,includingfunctionalrequirements,behavioralrequirements,operationalrequirements,and—aboveall—arealisticrangeofsecurityandreliabilitySystemandnetworkarchitecturesthatexplicitlyaddresstheserequirements.Soundarchitecturescanleadtosignificantcostandqualitybenefitsthroughoutthedevelopmentandlatersystemevolution.Asystemdevelopmentapproachthatexplicitlyaddressestheserequirements,pervasivelyandconsistentlythroughoutthedevelopment.。Useofprogramminglanguagesthatareinherentlyabletoavoidmanyofthecharacteristicflaws(suchasbufferoverflows,typemismatches,wildtransfers,concurrencyflaws,anddistributed-systemglitches)thattypicallyariseinunstructured,untyped,anderror-pronelanguagesandthatseemtoprevailoverdecades,throughnewsystemreleasesandnewsystems.Intelligentuseofcompilersandotherdevelopmenttoolsthathelpinidentifyingeliminatingadditionalflaws.However,sloppyprogrammingcansubverttheintentthesetools,andthesetools,andthusgoodprogrammingpracticeisstillExtensivedisciplineonthepartofdesigners,implementers,andmanagersthroughouttheentiresoftwaredevelopmentprocess.Thisultimatelyrequiresbetterintegrationofarchitecture,security,reliability,soundprogrammingtechniques,andsoftwareengineeringintothemainstreamofoureducationalandtrainingprograms.Pervasiveattentiontomaintainingconsistencywiththestatedrequirementsthroughoutoperation,administration,andmaintenance,despiteongoingsystemiterations.Somecombinationofformalandinformalapproachescanbeveryhelpfulinthisregard.Conceptually,manyproblemscanbeavoidedthroughsuitablychosenarchitectures,programminglanguages,compilers,andotheranalysistools—althoughultimately,theabilitiesofdesignersandprogrammersarealimitingfactor.Theanswertotheinitiallyposedquestionshouldnotbesurprisingtoanyonewhohashadconsiderableexperienceindevelopingsoftwarethatmustsatisfystringentrequirements.However,notethatalthoughthesamedisciplinecouldbeusedbythedevelopersofclosed-sourcesoftware,marketplaceforcestendtomakethismuchmoredifficultthanintheopensourceworld.Inparticular,thereseemstobeanincreasingtendencyamongthemass-marketproprietarysoftwaredeveloperstorushtomarket,whethertheproductisreadyornot—inessence,lettingthecustomersbethebetatesters.Furthermore,effortstoreducecostsoftenseemtoresultinlowest-common-denominatorproducts.Indeed,satisfyingstringentrequirementsforsecurityandreliability(forexample)isgenerallynotagoalthatyieldsmaximumprofits.Thus,forpracticalreasons,Iconcludethattheopen-sourceparadigmhassignificantpotentialthatismuchmoredifficulttoattaininclosed-sourceproprietarysystems.Thepotentialbenefitsofnonproprietarynonclosed-sourcesoftwarealsoincludetheabilitytomoreeasilycarryoutopenpeerreviews,addnewfunctionalityeitherlocallyortothemainlineproducts,identifyflaws,andfixthemrapidly—forexample,throughcollaborativeeffortsinvolvingpeopleirrespectiveoftheirgeographicallocationsandcorporateallegiances.Ofcourse,therisksincludeincreasedopportunitiesforevil-doerstodiscoverflawsthatcanbeexploited,andtoinserttrapdoorsandTrojanhorsesintothecode.Thusasensibleenvironmentmusthavemechanismsforensuringreliableandsecuresoftwaredistributionandlocalsystemintegrity.Itmustalsomakegooduseofsystemarchitectures,publickeyauthentication,cryptographicintegrityseals,cryptography,andtrustworthydescriptionsoftheprovenanceofindividualcomponentsandwhocryptography,andtrustworthydescriptionsoftheprovenanceofindividualcomponentsandwhohasmodifiedthem.Furtherresearchisneededonsystemsthatcanbepredictablycomposedoutofevaluatedcomponentsorthatcansurmountsomeofthevulnerabilitiesofthecomponents.Westillneedtoavoiddesignflawsandimplementationbugs,andtowarrantiesonsystemstodayaremostlyveryweak.Westilllackseriousmarketincentives.However,despiteallthechallenges,thepotentialbenefitsofrobustopen-sourcesoftwareareworthyofconsiderablecollaborativeeffort.Forafurtherfairlybalanceddiscussionoftherelativeadvantagesanddisadvantageswithrespecttoimprovingsecurity,seefivepapers(Lipner2000;McGraw2000;Neumann2000;Schneider2000;andWittenetal.2000)presentedatthe2000IEEESymposiumonSecurityandPrivacy.ThesessionwasorganizedandchairedbyLeeBadger.Thesecontributionsallessentiallyamplifytheprosand/orconsoutlinedhere.Lipnerexploressomerealbenefitsandsomesignificantdrawbacks.McGrawstatesflatlythat“openish”softwarewillnotreallyimprovesecurity.Schneidernotesthat“thelion’sshareofthevulnerabilitiescausedbysoftwarebugsiseasilydealtwithbymeansotherthansourcecodeinspections.”Healsoconsidersinhospitabilitywithbusinessmodels.TheWittenpaperexploreseconomics,metrics,andmodels.Inaddition,Neumann’sWebdevelopmentforcriticalrequirements,withparticularattentiontotherequirements,systemandnetworkarchitectures,anddevelopmentpractices.Inparticular,seeNeumann2004forareportforDARPA(summarizedbrieflyinNeumann2003a)ontheimportanceofarchitecturesinattainingprincipledassuredlytrustworthycomposablesystemsandnetworks,withparticularemphasisonopensourcebutwithgeneralapplicabilityaswell.ThatreportispartoftheDARPACHATSprogramoncomposablehigh-assurancetrustedsystems,whichisseriouslyaddressingmanyofthepromisingaspectsofmakingopen-sourcesoftwaremuchmorerobust.Furthermore,seethearchivesoftheACMRisksForum,asummaryindex(Neumann2003b)tocountlesscasesofsystemsthatfailedtoliveuptotheirrequirements,andananalysisofmanyoftheseriskscasesandwhatneedstobedonetominimizetherisks(Neumann1995).Itisanobvioustruismthatweshouldbelearningnottomakethesamemistakessoconsistently.Itisanequallyobvioustruismthattheselessonsarenotbeinglearned—mostspecificallywithrespecttoreliability,survivability,interoperability,andmanyother“-PeopleintheopensourceandfreesoftwarecommunityoftenarguethatmakingsourcecodePeopleintheopensourceandfreesoftwarecommunityoftenarguethatmakingsourcecodeavailabletoallisgoodforsecurity.Usersandexpertscanporeoverthecodeandfindvulnerabilities:“tomanyeyes,allbugsareshallow,”asEricRaymond(2001,41)putsit.Thisideaisnotentirelynew.Intheworldofcryptography,ithasbeenstandardpracticesincethenineteenthcenturytoassumethattheopponentknowsthedesignofyoursystem,sotheonlywayyoucankeephimoutisbydenyinghimknowledgeofatemporaryvariable,thekey(Kerckhoffs1883).However,opendesignisnotanideathateveryoneaccepts,evennow.Opponentsoffreesoftwarearguethat“ifthesoftwareisinthepublicdomain,thenpotentialhackershavealsohadtheopportunitytostudythesoftwarecloselytodetermineitsvulnerabilities”(Brown2002).Thisissueisnowassumingeconomicandpoliticalimportance,astheantitrustsettlementbetweenMicrosoftandtheDepartmentofJusticecompelsMicrosofttomakealotofinformationaboutinterfacesavailabletoitscompetitors—butwiththeprovisionthatdatawhosedisclosuremightprejudicesecuritymaybewithheld(Collar-Kotelly2002).Unsurprisingly,Microsoftisnowdiscoveringthatmanymoreaspectsofitssystemsaresecurity-relevantthanhadpreviouslybeenthought.Thereisarelatedissue:whetherinformationaboutdiscoveredvulnerabilitiesmaybepublished.InFebruary2003,Citibankobtainedaninjunctionprohibitinganyreportingofsecurityvulnerabilitiesofautomatictellermachinesystemsdisclosedbymyselfandtwocolleaguesatatrialwhichwewereattendingasexpertwitnesses.Thiswascounterproductiveforthebank,asitcompelledustopublishourattacksinaninvitedtalkandatechnicalreportinthedaysjustbeforethegagginghearing.Wewereslashdottedandthetechnicalreportwasdownloadedover110,000times(AndersonandBond2003;BondandZielinski2003).Butthisisunlikelytobethelasttimethatgaggingordersareusedagainstsecurityvulnerabilities;ifanything,theDigitalMillenniumCopyrightActandtheproposedEuropeanUnionDirectiveontheenforcementofintellectualpropertyrightswillmakethemevenmorecommon.Sothereisgrowingpublicinterestinthequestionofwhetheropennessisofmorevaluetotheattackerorthedefender.Thisquestionismuchmoregeneralthanwhethersoftwaresourcecodeshouldbeavailabletousers.Awiderangeofsystemsandcomponentscanbeeithereasierormoredifficulttotest,inspect,andrepair,dependingontheavailabletoolsandaccess.Hardwaredevicescanoftenbereverseengineeredsurprisinglylittleeffort—althoughthecapitalresourcesneededtofabricateaclonemightbescarce.Thedifferencebetween“open”and“closed”mayalsobelegalratherthantechnical;iflawsprohib