CTF Core Part 1 - PowerPoint PPT Presentation

Loading...

PPT – CTF Core Part 1 PowerPoint presentation | free to view - id: 77f0f-ZDc1Z



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

CTF Core Part 1

Description:

Wyvern: IP/FQDN: 132.216.68.2 / wyvern.campus.mcgill.ca ... Wyvern (continued): Fileserver. Volume Shadow copy setup coming soon ... – PowerPoint PPT presentation

Number of Views:60
Avg rating:3.0/5.0
Slides: 64
Provided by: jcp16
Category:
Tags: ctf | core | part | wyvern

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: CTF Core Part 1


1
CTF Core Part 1
  • Tuesday, October 19th, 2004
  • Jason Parente
  • CTF Servers
  • Microsoft Active Directory
  • The role of CTF
  • CTF Constitution/By-laws

2
CTF Servers
  • Nexus
  • IP/FQDN 132.216.68.5 / nexus.sus.mcgill.ca
  • Access Remote Desktop with Infopoint admin
    account.
  • Location BattleBridge (McConnell - 200N)
  • OS Windows 2000 Server
  • Administrators Rob David
  • CPU 2x300Mhz
  • Memory 256MB Ram
  • HD ??

3
CTF Servers
  • Nexus (continued)
  • DNS
  • DHCP
  • Infopoint Domain Active Directory
  • Notes This is a LEGACY system, who's use is
    nearing it's end. Hopefully, it will be taken
    down in the next few months. This server holds
    the taskforce admin accounts, ex rkaploadmin

4
CTF Servers
  • Wyvern
  • IP/FQDN 132.216.68.2 / wyvern.campus.mcgill.ca
  • Access Remote Desktop with campus account in
    Infopoint Admins group
  • Location BattleBridge (McConnell - 200N)
  • OS Windows 2003 Standard Server
  • Administrators Rob David
  • CPU 2xIntel Xeon 3.06Ghz
  • Memory 2.5GB Ram
  • HD 2x36GB SCSI for OS, 3x150GB (Raid-5) for
    I-drive

5
CTF Servers
  • Wyvern (continued)
  • Fileserver
  • Volume Shadow copy setup coming soon
  • Notes The I-drives and W-drives are held here,
    on a windows share. Recently deployed. Extremely
    potent machine.

6
CTF Servers
  • Iceberg
  • IP/FQDN 132.216.68.4 / iceberg.campus.mcgill.ca
  • Access Remote Desktop with campus account in
    Infopoint Admins group
  • Location BattleBridge (McConnell - 200N)
  • OS Windows 2000 Server
  • Administrators Rob David
  • CPU 2x200Mhz
  • Memory ??
  • HD ??

7
CTF Servers
  • Iceberg (continued)
  • Windows Print Server
  • Contains all shares of computers.

8
CTF Servers
  • Printserv
  • IP/FQDN 132.216.68.10 / printserv.sus.mcgill.ca
  • Access ssh, must have account on printserv
  • Location BattleBridge (McConnell - 200N)
  • OS Debian
  • Administrator Martin Stolle(Unofficially)
  • CPU 200Mhz
  • Memory 128MB Ram
  • HD ??

9
CTF Servers
  • Printserv (continued)
  • Linux Print Server
  • Use as last spool spot before printing to
    printer.
  • mst-ng.pl custom written perl script to sent
    printjob to correct printer,
    reduce quota.

10
CTF Servers
  • Tacos
  • IP/FQDN 132.216.68.17 / tacos.sus.mcgill.ca
  • Access ssh, account locally on Tacos
  • Location BattleBridge (McConnell - 200N)
  • OS Debian GNU/Linux Sarge
  • Administrator Martin Stolle (unofficially)
  • CPU 2x450Mhz (Pentium 3)
  • Memory 512MB Ram
  • HD 8Gb 18GB

11
CTF Servers
  • Tacos (continued)
  • Holds the home directory for the unix logins
  • CTF Personal Server
  • Members personal space
  • WebMP3
  • Webpics
  • CVS (Code repository)
  • Webmail (Squirrel mail)

12
CTF Servers
  • Titan
  • IP/FQDN 132.216.68.11 / titan.sus.mcgill.ca
  • Access ssh, or from Tacos
  • Location BattleBridge (McConnell - 200N)
  • OS Debian GNU/Linux
  • Administrator Martin Stolle, Unofficially
  • CPU ??
  • Memory ??
  • HD ??

13
CTF Servers
  • Titan (continued)
  • Internal file server
  • Contains personal storage (var/members)
  • Contains barchive (CTF archives) which includes
    ghost images, and other CTF files.

14
CTF Servers
  • Whitesnake
  • IP/FQDN 132.216.68.8 / whitesnake.sus.mcgill.ca
  • Access ssh, personal account on whitesnake
  • Location BattleBridge (McConnell - 200N)
  • OS Debian GNU/Linux Sarge
  • Administrator Nic Rob
  • CPU 2x P3-870Mhz
  • Memory 512MB Ram
  • HD ??

15
CTF Servers
  • Whitesnake (continued)
  • Apache Webserver. Hosts
  • All our main webpages
  • Department Webpages
  • Twiki
  • OTRS(Request Tracker)
  • Postgres Database server, used for Printing

16
CTF Servers
  • Iris
  • IP/FQDN 132.216.68.12 / iris.sus.mcgill.ca
  • Access ssh, personal account on iris
  • Location BattleBridge (McConnell - 200N)
  • OS Debian GNU/Linux Testing
  • Administrator Rob
  • CPU Celeron 850 Mhz
  • Memory 256MB Ram
  • HD ??

17
CTF Servers
  • Iris (continued)
  • Exim Mail Transfer Agent
  • Mailman Mailing list software
  • Spamassassin spam filter

18
Active Directory Services
  • What is Active Directory?
  • Object-based application
  • Tree-like

19
Active Directory Services
  • What is Active Directory?
  • Everything is an Object.
  • Users, computers, OUs, groups.
  • Its a gigantic database of objects.
  • Each object has properties.

20
Active Directory Services
  • What is Active Directory?
  • Objects are kept in Organizational Units (OU) and
    Containers.
  • Containers are used for
  • Delegation of administration rights
  • Ex Computers, Users
  • OUs are used for two purposes
  • Delegation of administration rights
  • Applying GPOs

21
Active Directory Services
  • What is Active Directory?
  • Group policies are a method to configure
    computers as a group.
  • Hundreds of different settings.
  • Currently used by CTF for
  • Folder Redirections (My Documents, Desktop,
    Favorites)

22
Active Directory Services
  • Accessing AD
  • Install the windows 2003 admin pak(google it)
  • Go to Administrative tools ? Active Directory
    Users Computers

23
Active Directory Services
  • Accessing Group Policy
  • Install the windows 2003 admin pak(google it)
  • Install the Group Policy Management console-gpmc
    (google it)
  • Go to Administrative tools ? group policy
    management

24
Active Directory Services
  • How it works?
  • Install AD
  • Create a Computer object in the appropriate OU.
    (Hint Check permissions to do this)
  • Change the following user or groups can add this
    computer to the domain to the correct user.
  • Add the client computer to AD
  • Must have same name as computer object created.
  • My Computer ? Right-click ? Properties. Computer
    Name (tab) ? Change ? add the domain name
    campus.mcgill.ca
  • Reboot.

25
Active Directory Services
  • Infopoint Domain
  • Previously used for all users on campus.
  • Currently contains the admin users account still
    used for CTF internal authentication.

26
Active Directory Services
  • Campus Domain
  • Currently the authentication domain used by CTF
    for student authentication.
  • Maintained by NCS.
  • The CTF OU OUfaculty groups, OUInfopoint,
    OUfaculty of science, CAcampus, CAmcgill,
    CAca
  • Must be a member of 520-Infopoint Admins to
    manage the OU.

27
Active Directory Services
  • Important CTF Groups
  • 520-2004exchangestudents Exchange students, we
    add them, they do not pay the 21st Century
    Computer Fund fee.
  • 520-Additional Users Big mess, for Paid and
    unusual account.
  • 520-PaidFall2004 Students who pay, 30 semester,
    for fall 2004.
  • 520-PROBLEMS science students who mcgill didnt
    add to 21st Century Computer Fund.
  • 520-Science Profs Profs in science that want
    access.

28
Active Directory Services
  • Important CTF Groups
  • Found under OUfaculty groups, OUInfopoint,
    OUfaculty of science, CAcampus, CAmcgill,
    CAca
  • 000-21stCenturyFund Contains all users in
    science
  • 520-Infopoint Admins People with special rights
    to the Infopoint OU
  • 520-Infopoint Users Full users members that can
    have full privileges on the Infopoint computers.
  • 520-Taskforce Internal Group of Taskforce
    Members, currently not used

29
Active Directory Services
  • Viewing groups membership
  • Right-click the group object and select
    properties.
  • Go to the Members tab
  • You will see a list of member

30
Active Directory Services
  • Viewing groups membership
  • Right-click the group object and select
    properties.
  • Go to the Members tab
  • You will see a list of members.
  • Adding members to groups
  • Right-click the group and choose add to group.
  • Type the first.last_at_mail.mcgill.ca of the user to
    add or the name of the group.

31
The Role of CTF
  • CTF is The McGill Science Computer Taskforce

32
The Role of CTF
  • CTF is The McGill Science Computer Taskforce
  • AKA officially known as the Science Undergraduate
    Society (SUS) Computer Taskforce. (but dont tell
    anyone).

33
The Role of CTF
  • The Mission
  • The Taskforces mandate is to provide campus wide
    information technology, innovations and user
    support to enhance the science students' learning
    experience at McGill University.
  • (CTF Constitution, article 2.1)

34
The Role of CTF
  • Aims (CTF Constitution article 2)
  • 2.2. The Taskforce shall coordinate the
    expenditure of the SUS McGill 21st Century
    Computer Fund in such a manner that it most
    benefits the science students in their academic
    environment.

35
The Role of CTF
  • Aims (CTF Constitution article 2)
  • 2.2. The Taskforce shall coordinate the
    expenditure of the SUS McGill 21st Century
    Computer Fund in such a manner that it most
    benefits the science students in their academic
    environment.
  • 2.3. To increase the students awareness to the
    services provided by the Taskforce.

36
The Role of CTF
  • Aims (CTF Constitution article 2)
  • 2.2. The Taskforce shall coordinate the
    expenditure of the SUS McGill 21st Century
    Computer Fund in such a manner that it most
    benefits the science students in their academic
    environment.
  • 2.3. To increase the students awareness to the
    services provided by the Taskforce.
  • 2.4. To increase the accessibility for students
    interested in participating with the Taskforce.

37
CTF Constitution
  • Important Articles
  • 3.User Eligibility
  • 3.1.All members of the SUS shall be eligible to
    the resources and services provided by the
    Taskforce.

38
CTF Constitution
  • Important Articles
  • 3.User Eligibility
  • 3.1.All members of the SUS shall be eligible to
    the resources and services provided by the
    Taskforce.
  • 3.2.Academic Staffs of the Faculty of Science of
    the University shall be eligible to the resources
    and services provided by the Taskforce.

39
CTF Constitution
  • Important Articles
  • 3.User Eligibility
  • 3.3.The Taskforce has the right to issue special
    accounts to persons within the McGill Community
    who have made contributions to the Taskforce in
    accordance to rules set in the By-laws.

40
CTF Constitution
  • Important Articles
  • 3.User Eligibility
  • 3.3.The Taskforce has the right to issue special
    accounts to persons within the McGill Community
    who have made contributions to the Taskforce in
    accordance to rules set in the By-laws.
  • 3.4.The Taskforce reserve the right to suspend or
    restrict users from accessing the resources it
    provides.

41
CTF Constitution
  • Important Articles
  • 7. Asset Management
  • 7.1 An up-to-date inventory in the format
    stipulated in the By-Laws shall be kept at all
    times to reflect the current possessions of the
    Computer Taskforce. Any missing parts shall be
    accounted for.

42
CTF Constitution
  • Important Articles
  • 7. Asset Management
  • 7.1 An up-to-date inventory in the format
    stipulated in the By-Laws shall be kept at all
    times to reflect the current possessions of the
    Computer Taskforce. Any missing parts shall be
    accounted for.
  • 7.2 The Inventory List shall be open to the
    General Council at all time, and shall be
    presented to the General Council at least once a
    year.

43
CTF Constitution
  • Important Articles
  • 7. Asset Management
  • 7.3 Auditing of the equipment inventory by a
    member of the General Council accompanied by the
    incoming Chairman will be performed before the
    last convened General Council session.

44
CTF Constitution
  • Important Articles
  • 8. Constituency
  • 8.1 The Taskforce shall be composed of
  • 8.1.1 Chairperson ("Chair")
  • 8.1.2 Associate Chairperson ("Associate Chair")
  • 8.1.3 Two members of GC present, one of which
    must be an executive such that preferably he or
    she will not graduate at the end of the academic
    year.
  • 8.1.4 An unspecified number of members of the
    general population of the SUS, to be determined
    by the Chair and Associate Chair

45
CTF Constitution
  • Important Articles
  • 8. Constituency
  • 8.1 The Taskforce shall be composed of
  • 8.1.5 An unspecified number of non-voting
    technical advisors who may be students, or
    academic or administrative staff of McGill
    University, to be determined by the Chair and
    Associate Chair
  • 8.1.6 One or Two Faculty Advisors selected by the
    Chair or Associate Chair and approved by the Dean
    of Science
  • 8.1.7 Special non-voting membership can be
    granted by the Chair and Associate Chair to
    individuals who demonstrate interests and
    abilities in promoting the aims of the Taskforce.

46
CTF Constitution
  • Important Articles
  • 9. Duties of the Taskforce Members
  • 9.1 The Chair shall
  • 9.1.1 Oversee the financial management of the
    Fund accounts, in conjunction with the Dean of
    Science
  • 9.1.2 Chair the Taskforce meetings
  • 9.1.3 Set the agenda for Taskforce meetings and
    inform all members as to the dates and times for
    these meetings at least two (2) school days in
    advance

47
CTF Constitution
  • Important Articles
  • 9. Duties of the Taskforce Members
  • 9.1 The Chair shall
  • 9.1.4 Coordinate all actions taken between
    meetings, and keep all members informed as to
    these actions
  • 9.1.5 Advise and instruct all members, to insure
    that they are able to perform their duties, and
    enable the Taskforce to be as effective as
    possible
  • 9.1.6 Act as an official liaison with any
    external bodies or persons
  • 9.1.7 Maintain and update the By-laws, and ensure
    distribution of and members adherence to the
    said document.

48
CTF Constitution
  • Important Articles
  • 9. Duties of the Taskforce Members
  • 9.2 The Associate Chair shall
  • 9.2.1 Assist the Chair in the performance of the
    duties outlined in Article 9.1
  • 9.2.2 Perform the duties of the Chair outlined in
    Article 9.1 when the Chair is unable to do so.
  • 9.2.3 Oversees the technical development of the
    projects initiated by the Taskforce.

49
CTF Constitution
  • Important Articles
  • 9. Duties of the Taskforce Members
  • 9.3 The members of GC shall
  • 9.3.1 Ensure the Taskforce is operating according
    to its constitutions and By-laws
  • 9.3.2 Act as liaison between the Taskforce and
    the SUS Executive Council.

50
CTF Constitution
  • Important Articles
  • 11 Replacement of Members
  • 11.1 If, for any reason, a member cannot continue
    his or her term, he or she shall be replaced in a
    manner as follows
  • 11.1.1 The Chair shall be replaced by the
    Associate Chair, who shall then become the Chair.
  • 11.1.2 The Associate Chair shall be replaced by a
    new Associate Chair who will be selected by the
    Taskforce by majority vote.
  • 11.1.3 The members of GC shall be replaced in
    accordance with Article 23 of the SUS
    Constitution.

51
CTF By-Laws I User Regulation
  • Article 2 User Conducts
  • 2.1 All users are expected to follow the
    regulation and code of conduct set by the
    Taskforce. The regulation should be posted on
    the Taskforce web site.

52
CTF By-Laws I User Regulation
  • Article 2 User Conducts
  • 2.1 All users are expected to follow the
    regulation and code of conduct set by the
    Taskforce. The regulation should be posted on
    the Taskforce web site.
  • 2.2 Any users who try to or successfully
    undermine the integrity of the McGill computer
    network and infrastructure through the use of the
    Infopoint Network or other Taskforce resources
    will be reported to the University for further
    actions against such behavior.

53
CTF By-Laws II Finance and Purchasing
Regulation
  • Article 1 Budget
  • Article 2 Financial Records
  • Article 3 Purchasing
  • Article 4 Inventory

54
CTF By-Laws III Members and Duties
  • Article 1 Member Conducts
  • 1.1 Members are expected to respect the privacy
    of the users.

55
CTF By-Laws III Members and Duties
  • Article 1 Member Conducts
  • 1.1 Members are expected to respect the privacy
    of the users.
  • 1.2 Members are expected to follow the
    regulations set by the University.

56
CTF By-Laws III Members and Duties
  • Article 1 Member Conducts
  • 1.1 Members are expected to respect the privacy
    of the users.
  • 1.2 Members are expected to follow the
    regulations set by the University.
  • 1.3 Members shall not break any laws using the
    Taskforce resources.

57
CTF By-Laws III Members and Duties
  • Article 1 Member Conducts
  • 1.4 Members are expected to be courteous to the
    users and to each other and maintain a
    professional attitude. Offending members will be
    expelled.

58
CTF By-Laws III Members and Duties
  • Article 1 Member Conducts
  • 1.4 Members are expected to be courteous to the
    users and to each other and maintain a
    professional attitude. Offending members will be
    expelled.
  • 1.5 Members are expected to respect the
    democratic nature of the Taskforce and shall not
    act in a unitary manner.

59
CTF By-Laws III Members and Duties
  • Article 2 Members Duties
  • 2.1 Members are expected to hold at least 3 hours
    of office duties.

60
CTF By-Laws III Members and Duties
  • Article 2 Members Duties
  • 2.1 Members are expected to hold at least 3 hours
    of office duties.
  • 2.2 Members are expected to show up to at least
    half of all the meetings called.

61
CTF By-Laws III Members and Duties
  • Article 2 Members Duties
  • 2.1 Members are expected to hold at least 3 hours
    of office duties.
  • 2.2 Members are expected to show up to at least
    half of all the meetings called.
  • 2.3 Members are expected to finish their assigned
    tasks within the allocated time.

62
CTF By-Laws III Members and Duties
  • Article 2 Members Duties
  • 2.4 Members are expected to research in group or
    alone for their projects

63
CTF By-Laws III Members and Duties
  • Article 2 Members Duties
  • 2.4 Members are expected to research in group or
    alone for their projects
  • 2.5 Members are expected to report their
    activities related to the Taskforce during the
    meetings.
About PowerShow.com