DOCSLIB.ORG

Network Administration IP Addresses

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Network Administration IP Addresses Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Outline Introduction Network Administration IP addresses Toward IPv6 Grégory Mounié Host name SCCI - Master-2 Routing <2013-09-17 mar.> Services Integration between different OS 1 / 75 2 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Challenge Introduction IP addresses For people with sufficient background: Toward IPv6 easy Chat on google talk (or facebook) with XMPP on wifi-campus/eduroam of the campus Host name hard Surf on ipv6.google.com on wifi-campus/eduroam of the campus Routing Services Integration between different OS 3 / 75 3 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Networks Networks of networks Definition (network) group of interconnected machines Definition (Internet) • network of networks • based on TCP (Transmission Control Protocol) and IP (Internet Protocol) protocols Figure : Interconnection of networks 4 / 75 5 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS TCP/IP IP address • unique number identifying a Network interface • eg. IPv6: 2a00:1450:4009:804::1007; Internet Protocol • IPv4: 74.125.230.130 • identifies network interfaces • eg. IPv6: fe80::2677:3ff:fe2e:22c0/64; • handles routing • IPv4: 192.168.0.1 • eg. IPv6: ; • fragmentation of data into packets ::1 • IPv4: 127.0.0.1 Transmission Control Protocol Two parts in a single number • transmissions in connected mode • fixed size number • error corrections, packets arriving in order • parts of variable length • beginning part : network ID • ending part : host ID 6 / 75 7 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS IP address notation Network IPv4 classes 3 classes of networks : the problem of the 3 bears IPv6 16 bytes, 128 bits, hexadecimal notation class A • few networks • lots of hosts • aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh • NNN.mmm.mmm.mmm • :: replace a single 0 sequence class B • not enough of middle size networks IPv4 4 bytes, 32 bits, decimal notation • NNN.NNN.mmm.mmm • aaa.bbb.ccc.ddd class C • lots of networks • few hosts • NNN.NNN.NNN.mmm 8 / 75 9 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Network mask Special IPv6 addresses • flexible network/machine ID size Which bits are used for network ID and which bits are used for host ID ? • 0:0:0:0:0:0:0:0, :: : host not specified • notation: =ip address=/X ; the X first bits are the network • FE80::/10 (truly /64) : link-local address (autoconf) address • FEC0::/10 : site-local address, non routed on Internet • IPv4 address mask denoted 255.255.255.0 • FF00::/8 : address multicast (0b1111111111111111111111100000000) • ::1/128 : loopback Various masks • ::FFFF:(IPv4 address) : double stack for IPv4 mapping • ::(IPv4 address) : IPv4 compatibility address • fe80::2677:3ff:fe2e:22c0/64 : 64 bits network ID • 255.255.255.0 : mask for IPv4 class C network • 255.0.0.0 : mask for IPv4 class A network • 255.128.0.0 : IPv4 mask: 9 bits for network, 23 bits for hosts 10 / 75 11 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Special IPv4 addresses Basic configuration • 0.0.0.0 : this host, or default • 0.host : un host of the local network • ifconfig command • 255.255.255.255 : local broadcast • ifconfig -a : list all available interfaces • PrefixNet.[1]+ : local broadcast • ip command • PrefixNet.PrefixSubnet.[1]+ : idem • ip link; ip addr • 127.x.x.x : loopback ifconfig eth0 add 2a00:1450:4007:803::1017/64 • 10/8, 172.16/12, 192.168/16 : private network ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up • 169.254.x.y : zeroconf (bonjour) autoconf (for local usage only) 12 / 75 13 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS From IPv4 to IPv6 IPv4 is a zombie IPv4 was dead long time ago ! • In 1993, IPv4 become classless : remaining C networks were • IPv4 name adress space is too small. grouped in (21 bits, 2048 hosts) networks and distributed • Transition path was planned with the IPv6 standard (RFC geographically : 2460, 1998): • Europe : 194-195.x.x.x • Dual stack public IP address during the transition • America : 198-199.x.x.x • Asia : 202-203.x.x.x Planned transition failure Large usage of private networks (NAT) • Nobody has done the transition. • All plan used double stack strategies. • Major architecture change. • No public IPv4 address anymore (IANA: 3 fev 2011 !) ! • One-way Internet connection for personal use: 1 public IP address per your DSL box (your CPE: customer premises equipment) • New services and protocols become undeployable ! 14 / 75 • Mobile phone routing (how to route efficiently multiple private 15 / 75 network ?) Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS IPv4 is a zombie II IPv4 is a zombi III Early adopters have a lot of remaining addresses NAT Zoo • people with competences have plenty of IPv4 adresses: • NAT44 : your home, your phone network • eg: recent wifi-campus and eduroam give one IPv4 address • NAT 444 : asia and africa : not a single public IP anymore ! per connected student • NAT 64 : early adopters • people without enough IPv4 address have not the competence • NAT 66 : NAT lovers to manage IPv6 network • NAT 464 ou 646 ?? 16 / 75 17 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Is IPv6 ready ? IPv6 Transition Big software are ready. (Chicken and eggs problem for small software) 5 main strategies: http://www.google.com/ipv6/statistics.html 1. full dual stack: not for everybody • 2% of google access (France 5%, Germany 4.5 %, Romania 2. tunnel: IPv6 over IPv4 to connect IPv6 islands 7.5%) • trouble with MTU 3. 6rd : CPE (your box) encapsulate IPv6 to the boundaries of http://6lab.cisco.com/stats/ the FAI • Free • France: 48% of prefix; 71.4% Transit AS; 50% Content; 5% 4. DS-Lite: the opposite of 6rd: encapsulate IPv4 packets in a users; IPv6 FAI network to the boundaries of the FAI. Grenoble academic science 5. NAT64: to connect to the remaining Internet from IPv6 only computer • IPv6 address space mapping of Grenoble universities and • very useful without IPv4 address (Mobile carrier soon ?) laboratories exists since 2001 • working at the main routers level • not deployed yet to end-user save exception 18 / 75 19 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Host names URL • Uniform Resource Locator • needed for human readable names • IP address may change ) name does not change • association between names and addresses • several names can be associated to the same address • several address can be associated to the same name Host name versus authentication A host name and its associated IP, are not sufficient as authentication ! 20 / 75 21 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Domain name Address resolving Domain Name System (DNS) • hierarchy • subdomains : en.wikipedia.org different mechanisms • recursive address resolution • configuration in /etc/nsswitch.conf • heavy use of caching • DNS servers IP : /etc/resolv.conf • slow propagation of changes (up to several days) • different addresses may be seen for a name if requests originate • /etc/hosts : list of known hosts from different places • may be the cause of process stall Host name versus authentication A host name and its associated IP, are not sufficient as authentication ! 22 / 75 23 / 75 Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS Introduction IP addresses Toward IPv6 Host name Routing Services Integration between different OS DNSSEC Private Network is not a protection • private IP ) no direct connection from Internet • still indirect connection are possible Browser + DNS attack • No security in the original design ) forged address by 1. Browsers download web pages including javascript code man-in-the-middle attack 2. Javascript code can connect only with the server • Digitally sign the record with public key cryptography and a 3. the server IP is given by the DNS of the server chain of trust (subdomain key is recursively authenticated
Load more

Recommended publications
  • Mobile Telemedicine and Wireless Remote Monitoring Applications
    İSTANBUL TECHNICAL UNIVERSITY INSTITUTE OF SCIENCE AND TECHNOLOGY MOBILE TELEMEDICINE AND WIRELESS REMOTE MONITORING APPLICATIONS M.Sc. Thesis by Taner SOYUGENÇ, B.Sc. Department : Electronics and Communication Engineering Programme : Biomedical Engineering NOVEMBER 2006 PREFACE In this project, my main goal is to implement a mobile sample application by defining the related global standards for telemedicine. The work is focused on recommendations of technology associated with a feasibility study. First of all, I would like to thank Assoc. Prof. Dr. Selçuk PAKER for his valuable advice, support and encouragement to accomplish the project. Besides, I would like to thank my family who is always with me giving support at every step of my life. November 2006 Taner SOYUGENÇ iii CONTENTS ACRONYMS vi LIST OF TABLES viii LIST OF FIGURES ix SUMMARY xi ÖZET xii 1. INTRODUCTION 1 1.1. Technology Overview 2 1.1.1. Communication Infrastructure 5 1.1.2. Overview of GSM-GPRS 6 1.1.2.1. Brief History of GSM 8 1.1.2.2. GPRS 12 1.1.3. Mobile Solutions 14 1.1.4. Wireless Medical Sensors 15 1.2. Aim of the Project 16 2. WORLDWIDE APPLICATIONS, VENDORS AND STANDARDS 18 2.1. Available Products 19 2.1.1. ECG 19 2.1.2. Pulse Oximeter 20 2.1.3. Blood Pressure Sensor 23 2.1.4. Various Sensor Brands 24 2.1.5. Advanced Research 27 2.1.6. Home Care Monitoring Systems 31 2.2. Medical Information Standards and Organizations 35 2.2.1. ASTM 39 2.2.2. CEN/TC251 Health Informatics 39 2.2.3.
    [Show full text]
  • Next Generation Web Scanning Presentation
    Next generation web scanning New Zealand: A case study First presented at KIWICON III 2009 By Andrew Horton aka urbanadventurer NZ Web Recon Goal: To scan all of New Zealand's web-space to see what's there. Requirements: – Targets – Scanning – Analysis Sounds easy, right? urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets What does 'NZ web-space' mean? It could mean: •Geographically within NZ regardless of the TLD •The .nz TLD hosted anywhere •All of the above For this scan it means, IPs geographically within NZ urbanadventurer (Andrew Horton) www.morningstarsecurity.com Finding Targets We need creative methods to find targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com DNS Zone Transfer urbanadventurer (Andrew Horton) www.morningstarsecurity.com Find IP addresses on IRC and by resolving lots of NZ websites 58.*.*.* 60.*.*.* 65.*.*.* 91.*.*.* 110.*.*.* 111.*.*.* 113.*.*.* 114.*.*.* 115.*.*.* 116.*.*.* 117.*.*.* 118.*.*.* 119.*.*.* 120.*.*.* 121.*.*.* 122.*.*.* 123.*.*.* 124.*.*.* 125.*.*.* 130.*.*.* 131.*.*.* 132.*.*.* 138.*.*.* 139.*.*.* 143.*.*.* 144.*.*.* 146.*.*.* 150.*.*.* 153.*.*.* 156.*.*.* 161.*.*.* 162.*.*.* 163.*.*.* 165.*.*.* 166.*.*.* 167.*.*.* 192.*.*.* 198.*.*.* 202.*.*.* 203.*.*.* 210.*.*.* 218.*.*.* 219.*.*.* 222.*.*.* 729,580,500 IPs. More than we want to try. urbanadventurer (Andrew Horton) www.morningstarsecurity.com IP address blocks in the IANA IPv4 Address Space Registry Prefix Designation Date Whois Status [1] -----
    [Show full text]
  • 공개sw 솔루션 목록(2015.6.30)
    OS/DBMS/WEB/WAS 공개SW 솔루션 목록(2015.6.30) 순번 분류 솔루션명 라이선스 기술지원 홈페이지 제품개요 1 DBMS C-JDBC LGPL community http://c-jdbc.ow2.org/ 데이터베이스 클러스터 2 DBMS DB4 오브젝트(db4o) GPL & dOCL prof/community http://www.db4o.com 객체지향 메모리 데이터베이스 엔진 GPL v2, GPL v3, 3 DBMS Drizzle community http://www.drizzle.org/ MySQL 6.0에서 파생된 RDBMS BSD 4 DBMS H2 EPL, MPL community http://www.h2database.com/ 자바기반 RDBMS HSQLDB 5 DBMS (Hyper Structured Query BSD community http://www.hsqldb.org 경량의 Java 기반 관계형 데이터베이스 Language Database) 데이터 웨어하우스, OLAP서버, BI 시스템 운용을 목적으 6 DBMS LucidDB GPL v2, LGPL v2 community http://luciddb.sourceforge.net 로 개발된 오픈소스 DBMS GPL v3, AGPL v3, 7 DBMS Neo4j community http://www.neo4j.org 그래프 데이터베이스 commercial AGPL v3, 8 DBMS VoltDB Proprietary prof/community http://voltdb.com/ 인메모리기반 RDBMS License 오픈소스 관계형 데이터베이스 관리 시스템. 9 DBMS 마리아DB(MariaDB) GPLv2, LGPL prof/community https://mariadb.org/ MySQL과 동일한 소스 코드를 기반 세계에서 가장 널리 사용되고 있는 대표적인 10 DBMS 마이에스큐엘(MySQL) GPL v2 prof/community http://www.mysql.com 관계형 데이터베이스 ※ prof : Professional Support(전문업체 기술지원) ※ community : Community Support(커뮤니티 기술지원) OS/DBMS/WEB/WAS 공개SW 솔루션 목록(2015.6.30) 순번 분류 솔루션명 라이선스 기술지원 홈페이지 제품개요 IBM에서 기증한 cloudscape 소스 기반으로 11 DBMS 아파치 더비(Apache Derby) Apache v2 community http://db.apache.org/derby/ 개발된 Java 기반의 관계형 데이터베이스 Berkeley 오라클 버클리 DB Database License http://www.oracle.com/kr/products/database/ 슬리피캣을 인수한 오라클에서 제공하는 12 DBMS prof/community (Oracle Berkeley DB) or berkeley-db/index.html 고성능 임베디드 데이터베이스 Sleepycat License GPL or Postgresql 데이터베이스의 기반으로 상용화된 13 DBMS 잉그레스(Ingres) prof/community
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Comparison of Web Server Software from Wikipedia, the Free Encyclopedia
    Create account Log in Article Talk Read Edit ViewM ohrisetory Search Comparison of web server software From Wikipedia, the free encyclopedia Main page This article is a comparison of web server software. Contents Featured content Contents [hide] Current events 1 Overview Random article 2 Features Donate to Wikipedia 3 Operating system support Wikimedia Shop 4 See also Interaction 5 References Help 6 External links About Wikipedia Community portal Recent changes Overview [edit] Contact page Tools Server Developed by Software license Last stable version Latest release date What links here AOLserver NaviSoft Mozilla 4.5.2 2012-09-19 Related changes Apache HTTP Server Apache Software Foundation Apache 2.4.10 2014-07-21 Upload file Special pages Apache Tomcat Apache Software Foundation Apache 7.0.53 2014-03-30 Permanent link Boa Paul Phillips GPL 0.94.13 2002-07-30 Page information Caudium The Caudium Group GPL 1.4.18 2012-02-24 Wikidata item Cite this page Cherokee HTTP Server Álvaro López Ortega GPL 1.2.103 2013-04-21 Hiawatha HTTP Server Hugo Leisink GPLv2 9.6 2014-06-01 Print/export Create a book HFS Rejetto GPL 2.2f 2009-02-17 Download as PDF IBM HTTP Server IBM Non-free proprietary 8.5.5 2013-06-14 Printable version Internet Information Services Microsoft Non-free proprietary 8.5 2013-09-09 Languages Jetty Eclipse Foundation Apache 9.1.4 2014-04-01 Čeština Jexus Bing Liu Non-free proprietary 5.5.2 2014-04-27 Galego Nederlands lighttpd Jan Kneschke (Incremental) BSD variant 1.4.35 2014-03-12 Português LiteSpeed Web Server LiteSpeed Technologies Non-free proprietary 4.2.3 2013-05-22 Русский Mongoose Cesanta Software GPLv2 / commercial 5.5 2014-10-28 中文 Edit links Monkey HTTP Server Monkey Software LGPLv2 1.5.1 2014-06-10 NaviServer Various Mozilla 1.1 4.99.6 2014-06-29 NCSA HTTPd Robert McCool Non-free proprietary 1.5.2a 1996 Nginx NGINX, Inc.
    [Show full text]
  • Installation and Configuration General Installation Considerations
    Installation and Configuration General Installation Considerations Before starting the installation, first you need to know what do you want to use PHP for. There are three main fields you can use PHP, as described in the What can PHP do? section: • Websites and web applications (server-side scripting) • Command line scripting • Desktop (GUI) applications For the first and most common form, you need three things: PHP itself, a web server and a web browser. You probably already have a web browser, and depending on your operating system setup, you may also have a web server (e.g. Apache on Linux and MacOS X; IIS on Windows). You may also rent webspace at a company. This way, you don't need to set up anything on your own, only write your PHP scripts, upload it to the server you rent, and see the results in your browser. In case of setting up the server and PHP on your own, you have two choices for the method of connecting PHP to the server. For many servers PHP has a direct module interface (also called SAPI). These servers include Apache, Microsoft Internet Information Server, Netscape and iPlanet servers. Many other servers have support for ISAPI, the Microsoft module interface (OmniHTTPd for example). If PHP has no module support for your web server, you can always use it as a CGI or FastCGI processor. This means you set up your server to use the CGI executable of PHP to process all PHP file requests on the server. If you are also interested to use PHP for command line scripting (e.g.
    [Show full text]
  • Strong Dependencies Between Software Components
    Specific Targeted Research Project Contract no.214898 Seventh Framework Programme: FP7-ICT-2007-1 Technical Report 0002 MANCOOSI Managing the Complexity of the Open Source Infrastructure Strong Dependencies between Software Components Pietro Abate ([email protected]) Jaap Boender ([email protected]) Roberto Di Cosmo ([email protected]) Stefano Zacchiroli ([email protected]) Universit`eParis Diderot, PPS UMR 7126, Paris, France May 24, 2009 Web site: www.mancoosi.org Contents 1 Introduction . .2 2 Strong dependencies . .3 3 Strong dependencies in Debian . .7 3.1 Strong vs direct sensitivity: exceptions . .9 3.2 Using strong dominance to cluster data . 11 3.3 Debian is a small world . 11 4 Efficient computation . 12 5 Applications . 13 6 Related works . 16 7 Conclusion and future work . 17 8 Acknowledgements . 18 A Case Study: Evaluation of debian structure . 21 Abstract Component-based systems often describe context requirements in terms of explicit inter-component dependencies. Studying large instances of such systems|such as free and open source software (FOSS) distributions|in terms of declared dependencies between packages is appealing. It is however also misleading when the language to express dependencies is as expressive as boolean formulae, which is often the case. In such settings, a more appropriate notion of component dependency exists: strong dependency. This paper introduces such notion as a first step towards modeling semantic, rather then syntactic, inter-component relationships. Furthermore, a notion of component sensitivity is derived from strong dependencies, with ap- plications to quality assurance and to the evaluation of upgrade risks. An empirical study of strong dependencies and sensitivity is presented, in the context of one of the largest, freely available, component-based system.
    [Show full text]
  • Migration from Windows to Linux for a Small Engineering Firm "A&G Associates"
    Rochester Institute of Technology RIT Scholar Works Theses 2004 Migration from Windows to Linux for a small engineering firm "A&G Associates" Trimbak Vohra Follow this and additional works at: https://scholarworks.rit.edu/theses Recommended Citation Vohra, Trimbak, "Migration from Windows to Linux for a small engineering firm A&G" Associates"" (2004). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. Migration from Windows to Linux for a Small Engineering Firm "A&G Associates" (H ' _T ^^L. WBBmBmBBBBmb- Windows Linux by Trimbak Vohra Thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in Information Technology Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences Date: December 2, 2004 12/B2/28B2 14:46 5854752181 RIT INFORMATION TECH PAGE 02 Rochester Institute of Teehnology B. Thomas Golisano College of Computing and Information Sciences Master of Science in Information Technology Thesis Approval Form Student Name: Trimbak Vohra Thesis Title: Migration from Windows to Unux for a Small Engineeriog Firm "A&G Associates" Thesis Committee Name Signature Date Luther Troell luther IrQell, Ph.D ttL ",j7/Uy Chair G. L. Barido Prof. ~~orge Barido ? - Dec:. -cl7' Committee Member Thomas Oxford Mr. Thomas OxfocQ \ 2. L~( Q~ Committee Member Thesis Reproduction Permission Form Rochester Institute of Technology B. Thomas Golisano College of Computing and Information Sciences Master of Science in Information Technology Migration from Windows to Linux for a Small Engineering Firm "A&G Associates" I,Trimbak Vohra, hereby grant permission to the Wallace Library of the Rochester Institute of Technology to reproduce my thesis in whole or in part.
    [Show full text]
  • PHP Version 5.6.26
    7/24/2018 phpinfo() PHP Version 5.6.26 System Linux omapl138-lcdk 4.9.28-geed43d1050 #1 PREEMPT Wed Jul 4 12:10:54 BST 2018 armv5tejl Build Date Jun 28 2017 18:05:04 Configure Command '../php-5.6.26/configure' '--build=x86_64-linux' '--host=arm-linux-gnueabi' '--target=arm-linux-gnueabi' '--prefix=/usr' '--exec_prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--libexecdir=/usr/libexec' '--datadir=/usr/share' '-- sysconfdir=/etc' '--sharedstatedir=/com' '--localstatedir=/var' '--libdir=/usr/lib' '--includedir=/usr/include' '-- oldincludedir=/usr/include' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--disable-silent-rules' '--disable- dependency-tracking' '--with-libtool-sysroot=/home/gtbldadm/processor-sdk-linux-morty-build/build-ARM9_1/arago- tmp-external-linaro-toolchain/sysroots/omapl138-lcdk' '--enable-mbstring' '--enable-wddx' '--enable-zip' '--with- libdir=lib' '--with-gettext=/home/gtbldadm/processor-sdk-linux-morty-build/build-ARM9_1/arago-tmp-external-linaro- toolchain/sysroots/omapl138-lcdk/usr/lib/..' '--with-zlib=/home/gtbldadm/processor-sdk-linux-morty-build/build- ARM9_1/arago-tmp-external-linaro-toolchain/sysroots/omapl138-lcdk/usr/lib/..' '--with- iconv=/home/gtbldadm/processor-sdk-linux-morty-build/build-ARM9_1/arago-tmp-external-linaro- toolchain/sysroots/omapl138-lcdk/usr/lib/..' '--with-mcrypt=/home/gtbldadm/processor-sdk-linux-morty-build/build- ARM9_1/arago-tmp-external-linaro-toolchain/sysroots/omapl138-lcdk/usr' '--with-bz2=/home/gtbldadm/processor- sdk-linux-morty-build/build-ARM9_1/arago-tmp-external-linaro-toolchain/sysroots/omapl138-lcdk/usr'
    [Show full text]
  • Towards Automated Privilege Separation
    Towards Automated Privilege Separation Dhananjay Bapat, Kevin Butler, and Patrick McDaniel Department of Computer Science and Engineering The Pennsylvania State University University Park, PA 16802 USA dbapat,butler,[email protected] Abstract. Applications are subject to threat from a number of attack vectors, and limiting their attack surface is vital. By using privilege sep- aration to constrain application access to protected resources, we can mitigate the threats against the application. Previous examinations of privilege separation either entailed significant manual effort or required access to the source code. We consider a method of performing privilege separation through black-box analysis. We consider similar applications to the target and infer states of execution, and determine unique trigger system calls that cause transitions. We use these for the basis of state- based policy enforcement by leveraging the Systrace policy enforcement mechanism. Our results show that we can infer state transitions with a high degree of accuracy, while our modifications to Systrace result in more granular protection by limiting system calls depending on the ap- plication’s state. The modified Systrace increases the size of the Apache web server’s policy file by less than 17.5%. 1 Introduction Applications in computing environments are often insecure. Insecure applications open the system and user data to exploitation. The number of attack vectors, from buffer overflow attacks to worms and other malware, is large and growing. However, the system can defend itself against attack and reduce the amount of potential damage by limiting an application’s access to trusted system resources. In Unix systems, an application runs at the same privilege level as that of the user executing it.
    [Show full text]
  • BTP Stage - I 4Th Report
    BTP Stage - I 4th Report Sandeep Prasad 03D05011 s [email protected] March 18, 2013 Introduction Two main components of Clicker architecture are web-server and database-server. For our architecture we will assume Linux as the operating system. In this report we will inspect various features of web-servers. Mapping of features of web-server and requirements of Clicker will assist in narrowing down of list of web-servers appropriate for Clicker software. Requirements of Clicker Software In current architecture the requirements that are taken accounted for are 1. Multiple concurrent sessions: One login and corresponding logout from web server is considered as one session, session is between user and web server. 2. Multiple concurrent connections: One login and corresponding logout from database server is considered as one connection. Connection is between web server and database server. Features of Web-Server Mentioned below are some of the features that a web-server is supposed to provide 1. basic access authentication: A method for HTTP user agent to provide a username and password when making a request 2. digest access authentication: applying function to password before sending it over the network, unlike basic access authentication which sends plain text 3. mode: Web-server can be either kernel-mode or user mode. 1 Kernel-mode Kernel mode web-server is implemented into OS kernel, servers like TUX on GNU/Linux or Microsoft IIS on windows are example of kernel-mode server. Ker- nel mode server can use all the hardware resources it needs such as non-paged memory, CPU time-slices, network adapters, buffer, etc directly, thus they usually work faster.
    [Show full text]
  • Padanan Aplikasi Dan Server Windows Di Linux
    PPaaddaannaann AApplliikkaassii ddaann SSeerrvveerr WWiinnddoowwss ddii LLiinnuuxx Romi Satria Wahono [email protected] http://romisatriawahono.net Lisensi Dokumen: Copyright © 2003-2006 IlmuKomputer.Com Seluruh dokumen di IlmuKomputer.Com dapat digunakan, dimodifikasi dan disebarkan secara bebas untuk tujuan bukan komersial (nonprofit), dengan syarat tidak menghapus atau merubah atribut penulis dan pernyataan copyright yang disertakan dalam setiap dokumen. Tidak diperbolehkan melakukan penulisan ulang, kecuali mendapatkan ijin terlebih dahulu dari IlmuKomputer.Com. Padanan aplikasi adalah isu yang paling sering ditanyakan bagi orang yang melakukan migrasi dari Windows ke Linux. Tulisan ini akan menampilkan padanan aplikasi Windows di Linux dalam beberapa kategori, diantaranya adalah aplikasi networking, mulitmedia dan grafis, desktop, office, game, scientific, dan emulator. Banyak aktifis Linux yang membuat daftar padanan aplikasi Windows di Linux, diantaranya yang terkenal dan cukup lengkap adalah yang dibuat oleh Valery V. Kachurov (http://www.linuxrsp.ru/win-lin-soft/table-eng.html). Artikel ini akan merangkumkan dan mengkompilasi ulang padanan aplikasi dan server dari berbagai sumber. 1. Aplikasi Networking Kategori Aplikasi di Windows Aplikasi di Linux [Download] Web Browser Internet Explorer, Mozilla, Opera, Konqueror Firebird, Lynx Mozilla [mozilla.org] Galeon [galeon.sourceforge.net] Opera [opera.com] Firebird [mozilla.org/projects/firebird] Nautilus [gnome.org/projects/nautilus] Epiphany [gnome.org/projects/epiphany]
    [Show full text]