ICO wiki - User contributions [en]

User:Avaba

2017-04-12T18:30:59Z

Avaba: Created page with "Test"

Test

User:Eocakovs

2017-03-15T11:02:47Z

Avaba: /* Non-Functional */

= I701 - Information System Analysis =

== Group Project ==

====Members====
* Ardi Vaba
* Pascal Tietjen
* Peep Kuulme
* Nika Ptskialadze
* Erik Ocakovskih
* Frank Korving

====Organization====
WPE (Windows Programs Explained)

'''Daily Operations:''' 
We are a software development company. Our current major project consists of providing and supporting an application with simple interface to analyze currently installed programs on the system. 

'''Example Information Systems:''' 
Accounting Information System 
Customer Support Information System 
Sales Information System 
Developer Daily-Work Information System 
Transaction Processing Information System 

====Value Chain Analysis====

'''Primary Activities:''' 
''Direct''
* Software Development [Getting the software to working state]
* Software Delivery [Getting the product to the market]
* Sales [Selling a product to current customers and new customer aquisition]
* Marketing [Providing product information to target group]
''Indirect''
* Scheduling [Optimizing work and workload assignments]
* Support / Service [Maintenance of existing software and customer assistance]
* Marketing [Customer Management]
''Quality Assurance''
* Testing [Functionality verification of the developed working software]

 
'''Support Activities:''' 
''Direct''
* Infrastructure [Providing Legal, Administrative and Accounting support]
* Procurement [Acquisition of external services]
''Indirect''
* HR Management [Human Resource Management]
 

====IT SWOT====

{| class="wikitable"
|-
! Strength
! Weakness
! Opportunities
! Threats
|-
| Innovative - no other popular program like this
| No brand recognition
| Globally extending
| Larger company might sprint past with a similar program
|-
| Strong team - well organized, good
| Small company not a lot of financial backup
| Expand the team for faster development
| Sustainable financial backing
|-
| Competitively priced
| Development slow due to the size of the company
| Targeting industries
| Customer scepticisim - do not want to give access to scan their computer
|-
| User-friendly interface
| Organic growth - no outside funding
|
|
|}

====Improvements====

'''Problems:''' 
* Application Information
** Due to lack of program information / Methods of updating
** Trustworthiness / Unknown Sources
** Customer Perception of the Products [Solution should provide: Transparency for customers / Awareness of Application]
* Market access / interactions

====Short Information System Description====

Information System will provide Windows OS users with detailed information on their installed packages and applications. Provided information will include trustworthiness / rating / availability / checksum / developer details of the application. System will incentivize users and developers to submit descriptions of applications, which would go through a review process before publication. Companies can become verified by us through a paid application verification process thereby granting "trust-ability" to these applications and their developers. Users can subscribe to a live-scanning service which will notify them when any installed packages are compromised or need to be updated.

===Requirements===
====Functional====
''''Users''''
* Users should be able to subscribe to paid services
* Users should be able to scan their computer and check for installed programs
* Users should be able to gain information on these installed programs through us (WPE)
* Users should be able to delete the application
* Users should be able to request suggestions on alternative
* Users should be able to search for similar applications
* Users should be able to search for any application
* Users should be able to submit their rating/opinion to be reviewed by us

''''Companies''''
* Companies should be able to apply for verification
* Companies should be able to submit their own description after verification

====Non-Functional====
(Draft)
* Application shall be operable even in case remote services become unreachable
* All the information shall be as transparent to user as possible
* Every aspect of the software shall be testable
* User experience of the software shall be as responsive as possible
* User privacy shall be completely protected
* Documentation of software shall be easily understood by new developers
* Software shall be safe to operate by non technical people
* Application shall be safely and intuitively operable by 8 year old with minimal technical knowledge
or
* Operability of the software should be as straight forward as possible

===User Stories===
* User needs to find specific information on an installed application, enters name into search bar and presses search-button.
* User finds application, selects it and presses view detailed information button.
* User sees no specific details about application and presses "request additional information"-button.
* User looks through provided information, wants to remove the application and presses the "uninstall"-button, confirmation dialogue appears and user confirms his decision.
* User wants to find possible similar applications, presses "similar apps"-button.
* Premium user sees notification presses it and opens up a tab with an active analysis of host system.
* Non-premium user wants to get premium-features, switches to premium-features section which displays features and payment information.
* User selects preferred amount and payment method from premium-features section which opens up an external browser with preferred payment method's website.
* User wants to change how application updates, opens the update options from the settings menu and selects the "ask-for-confirmation-before-update" method.
* User wants to install a program and check whether the developer is verified or not so searches for the verification signature in the application details.
* User wants to leave feedback on specific application, clicks "leave feedback" button in the application information details tab that opens up a text-box, the user enters feedback and presses submit button.

Use Case: Prerequisites / Expected results

Add high user case diagram / Use case high level view

User:Eocakovs

2017-03-15T11:02:29Z

Avaba: /* Non-Functional */

= I701 - Information System Analysis =

== Group Project ==

====Members====
* Ardi Vaba
* Pascal Tietjen
* Peep Kuulme
* Nika Ptskialadze
* Erik Ocakovskih
* Frank Korving

====Organization====
WPE (Windows Programs Explained)

'''Daily Operations:''' 
We are a software development company. Our current major project consists of providing and supporting an application with simple interface to analyze currently installed programs on the system. 

'''Example Information Systems:''' 
Accounting Information System 
Customer Support Information System 
Sales Information System 
Developer Daily-Work Information System 
Transaction Processing Information System 

====Value Chain Analysis====

'''Primary Activities:''' 
''Direct''
* Software Development [Getting the software to working state]
* Software Delivery [Getting the product to the market]
* Sales [Selling a product to current customers and new customer aquisition]
* Marketing [Providing product information to target group]
''Indirect''
* Scheduling [Optimizing work and workload assignments]
* Support / Service [Maintenance of existing software and customer assistance]
* Marketing [Customer Management]
''Quality Assurance''
* Testing [Functionality verification of the developed working software]

 
'''Support Activities:''' 
''Direct''
* Infrastructure [Providing Legal, Administrative and Accounting support]
* Procurement [Acquisition of external services]
''Indirect''
* HR Management [Human Resource Management]
 

====IT SWOT====

{| class="wikitable"
|-
! Strength
! Weakness
! Opportunities
! Threats
|-
| Innovative - no other popular program like this
| No brand recognition
| Globally extending
| Larger company might sprint past with a similar program
|-
| Strong team - well organized, good
| Small company not a lot of financial backup
| Expand the team for faster development
| Sustainable financial backing
|-
| Competitively priced
| Development slow due to the size of the company
| Targeting industries
| Customer scepticisim - do not want to give access to scan their computer
|-
| User-friendly interface
| Organic growth - no outside funding
|
|
|}

====Improvements====

'''Problems:''' 
* Application Information
** Due to lack of program information / Methods of updating
** Trustworthiness / Unknown Sources
** Customer Perception of the Products [Solution should provide: Transparency for customers / Awareness of Application]
* Market access / interactions

====Short Information System Description====

Information System will provide Windows OS users with detailed information on their installed packages and applications. Provided information will include trustworthiness / rating / availability / checksum / developer details of the application. System will incentivize users and developers to submit descriptions of applications, which would go through a review process before publication. Companies can become verified by us through a paid application verification process thereby granting "trust-ability" to these applications and their developers. Users can subscribe to a live-scanning service which will notify them when any installed packages are compromised or need to be updated.

===Requirements===
====Functional====
''''Users''''
* Users should be able to subscribe to paid services
* Users should be able to scan their computer and check for installed programs
* Users should be able to gain information on these installed programs through us (WPE)
* Users should be able to delete the application
* Users should be able to request suggestions on alternative
* Users should be able to search for similar applications
* Users should be able to search for any application
* Users should be able to submit their rating/opinion to be reviewed by us

''''Companies''''
* Companies should be able to apply for verification
* Companies should be able to submit their own description after verification

====Non-Functional====
(Draft)
* Application shall be safely and intuitively operable by 8 year old with minimal technical knowledge
or
* Operability of the software should be as straight forward as possible
*
* Application shall be operable even in case remote services become unreachable
* All the information shall be as transparent to user as possible
* Every aspect of the software shall be testable
* User experience of the software shall be as responsive as possible
* User privacy shall be completely protected
* Documentation of software shall be easily understood by new developers
* Software shall be safe to operate by non technical people

===User Stories===
* User needs to find specific information on an installed application, enters name into search bar and presses search-button.
* User finds application, selects it and presses view detailed information button.
* User sees no specific details about application and presses "request additional information"-button.
* User looks through provided information, wants to remove the application and presses the "uninstall"-button, confirmation dialogue appears and user confirms his decision.
* User wants to find possible similar applications, presses "similar apps"-button.
* Premium user sees notification presses it and opens up a tab with an active analysis of host system.
* Non-premium user wants to get premium-features, switches to premium-features section which displays features and payment information.
* User selects preferred amount and payment method from premium-features section which opens up an external browser with preferred payment method's website.
* User wants to change how application updates, opens the update options from the settings menu and selects the "ask-for-confirmation-before-update" method.
* User wants to install a program and check whether the developer is verified or not so searches for the verification signature in the application details.
* User wants to leave feedback on specific application, clicks "leave feedback" button in the application information details tab that opens up a text-box, the user enters feedback and presses submit button.

Use Case: Prerequisites / Expected results

Add high user case diagram / Use case high level view

User:Eocakovs

2017-03-15T11:02:06Z

Avaba: /* Non-Functional */

= I701 - Information System Analysis =

== Group Project ==

====Members====
* Ardi Vaba
* Pascal Tietjen
* Peep Kuulme
* Nika Ptskialadze
* Erik Ocakovskih
* Frank Korving

====Organization====
WPE (Windows Programs Explained)

'''Daily Operations:''' 
We are a software development company. Our current major project consists of providing and supporting an application with simple interface to analyze currently installed programs on the system. 

'''Example Information Systems:''' 
Accounting Information System 
Customer Support Information System 
Sales Information System 
Developer Daily-Work Information System 
Transaction Processing Information System 

====Value Chain Analysis====

'''Primary Activities:''' 
''Direct''
* Software Development [Getting the software to working state]
* Software Delivery [Getting the product to the market]
* Sales [Selling a product to current customers and new customer aquisition]
* Marketing [Providing product information to target group]
''Indirect''
* Scheduling [Optimizing work and workload assignments]
* Support / Service [Maintenance of existing software and customer assistance]
* Marketing [Customer Management]
''Quality Assurance''
* Testing [Functionality verification of the developed working software]

 
'''Support Activities:''' 
''Direct''
* Infrastructure [Providing Legal, Administrative and Accounting support]
* Procurement [Acquisition of external services]
''Indirect''
* HR Management [Human Resource Management]
 

====IT SWOT====

{| class="wikitable"
|-
! Strength
! Weakness
! Opportunities
! Threats
|-
| Innovative - no other popular program like this
| No brand recognition
| Globally extending
| Larger company might sprint past with a similar program
|-
| Strong team - well organized, good
| Small company not a lot of financial backup
| Expand the team for faster development
| Sustainable financial backing
|-
| Competitively priced
| Development slow due to the size of the company
| Targeting industries
| Customer scepticisim - do not want to give access to scan their computer
|-
| User-friendly interface
| Organic growth - no outside funding
|
|
|}

====Improvements====

'''Problems:''' 
* Application Information
** Due to lack of program information / Methods of updating
** Trustworthiness / Unknown Sources
** Customer Perception of the Products [Solution should provide: Transparency for customers / Awareness of Application]
* Market access / interactions

====Short Information System Description====

Information System will provide Windows OS users with detailed information on their installed packages and applications. Provided information will include trustworthiness / rating / availability / checksum / developer details of the application. System will incentivize users and developers to submit descriptions of applications, which would go through a review process before publication. Companies can become verified by us through a paid application verification process thereby granting "trust-ability" to these applications and their developers. Users can subscribe to a live-scanning service which will notify them when any installed packages are compromised or need to be updated.

===Requirements===
====Functional====
''''Users''''
* Users should be able to subscribe to paid services
* Users should be able to scan their computer and check for installed programs
* Users should be able to gain information on these installed programs through us (WPE)
* Users should be able to delete the application
* Users should be able to request suggestions on alternative
* Users should be able to search for similar applications
* Users should be able to search for any application
* Users should be able to submit their rating/opinion to be reviewed by us

''''Companies''''
* Companies should be able to apply for verification
* Companies should be able to submit their own description after verification

====Non-Functional====
* Application shall be safely and intuitively operable by 8 year old with minimal technical knowledge
or
* Operability of the software should be as straight forward as possible

* Application shall be operable even in case remote services become unreachable
* All the information shall be as transparent to user as possible
* Every aspect of the software shall be testable
* User experience of the software shall be as responsive as possible
* User privacy shall be completely protected
* Documentation of software shall be easily understood by new developers
* Software shall be safe to operate by non technical people

===User Stories===
* User needs to find specific information on an installed application, enters name into search bar and presses search-button.
* User finds application, selects it and presses view detailed information button.
* User sees no specific details about application and presses "request additional information"-button.
* User looks through provided information, wants to remove the application and presses the "uninstall"-button, confirmation dialogue appears and user confirms his decision.
* User wants to find possible similar applications, presses "similar apps"-button.
* Premium user sees notification presses it and opens up a tab with an active analysis of host system.
* Non-premium user wants to get premium-features, switches to premium-features section which displays features and payment information.
* User selects preferred amount and payment method from premium-features section which opens up an external browser with preferred payment method's website.
* User wants to change how application updates, opens the update options from the settings menu and selects the "ask-for-confirmation-before-update" method.
* User wants to install a program and check whether the developer is verified or not so searches for the verification signature in the application details.
* User wants to leave feedback on specific application, clicks "leave feedback" button in the application information details tab that opens up a text-box, the user enters feedback and presses submit button.

Use Case: Prerequisites / Expected results

Add high user case diagram / Use case high level view

Category:I805 Authentication and Authorization

2017-02-07T10:09:42Z

Avaba: /* General information */

=Authentication and Authorization=

==General information==

In this course we continue where we left off with [https://wiki.itcollege.ee/index.php/Category:I802_Firewalls_and_VPN_IPSec#Firewalls_and_VPN.2FIPSec Firewalls and VPN/IPsec] course.

Relevant topics for research and implementation in the lab.
Lectures coming up for most of the topics:

* File based password stores eg. /etc/shadow, .htaccess
* Signing and encrypting e-mail using GPG
* Active Directory protocols: LM, NTLM, Kerberos, GSSAPI, SPNEGO, LDAP
* More TLS and client side authentication in particular
* Filesystem permissions: access control lists, selinux, apparmor
* RADIUS
* Multi-factor authentication: smartcards, Yubikey, Mobile-ID, etc
* Contactless cards
* On the web: Cookies, OAuth, OpenID, iPizza,

Intro slides & video recording:

https://docs.google.com/presentation/d/1NzY8AspqZwrYxoJ3Qi-pBWsMDdiIUeA4lgZnwZGTMVg/edit?usp=sharing

https://echo360.e-ope.ee/ess/echo/presentation/54eb478c-f6ae-4629-b1e3-c43f5a2f6842?ec=true

Tasks, not necessarily all have to be covered. Pick the one you like the most:

* Play the red team: Kustas, Ender, Mikus
* Set up rocket.chat instead of IRC server: Meelis Hass
* Set up file synchronization with NextCloud: <insert your name here>
* Reconfigure Gogs: <insert your name here>
* Reconfigure wiki: <insert your name here>
* Reconfigure mail server: <insert your name here>
* Reconfigure webserver/MySQL: Joosep
* Set up domain controller replication between servers
* Set a blank smartcard as TLS client authentication token: <insert your name here>
* NFC card backups: <insert your name here>
* OpenVPN with Estonian ID-card howto: Ardi Vaba
* Set up OpenWrt wifi routers as access points with username/password authentication (like eduroam wireless network): <insert your name here>

With Lauri/Belgin from Linux/Windows admin course:

* Set up domain controller /w MS AD/Samba:
* Set up fileserver with several shares: <insert your name>
* Use iMac and HP Probook at 412/411 for joining them to domain. Needs some network rewiring first, ask Lauri.
* Set up group policies, eg install software and configure VPN for HP Probook

With Viktor from Incident management course:

* Set up incident management software, configure to authenticate with AD

ECTS: 4

Lecturers: Lauri Võsandi

OSadmin wiki article

2017-01-30T10:48:30Z

Avaba: /* Chosen topics */

=Intro=
*Choose a topic from personal experience related with the subject or from topics found on the wiki page
*[[#Chosen_topics|Write the topic here]].
*Lecturer will confirm the topic
*Write your article in wiki environment
*Inform the [[Operating_systems#Lecturer|lecturer]] when the article is finished
*Receive feedback for corrections

=Requirements for the wiki article=
Author: name, group and date when the article is written

==Introduction ==
Covers points what will be discussed in the article, what are the requirements for the article reader; what are the operating system’s requirements.

==Contents==
All commands should be easily separable from the overall text.
Users should be able to copy the commands directly (additional info like prompt and user distinction symbols should be left out from the command description area)
The text should determine what user permissions are needed to perform these tasks.
The reader of your article is your fellow students, so try to avoid irrelevant information and stay on topic (don’t explain the meaning of IP address or how to install Ubuntu, when your topic is actually about htop)
All the content should be referenced.
Do not use slang and try to be grammatically correct. 

Bear in mind that this is an open environment, so everything you write in your wiki article, will be public. 

==Referencing==
Best practises of wiki referencing should be used.
Terms are but between square brackets to reference other articles in the system.
All drawing and images have to be referenced below the picture and in the text. (for example “System architecture can be viewed on image x, y and z.”)
Author’s own ideas have to be clearly presentable. Everything used from the sources have to be referenced.

==Fellow student review==
Please find a fellow student who will review your article and give a feedback on the discussion tab of the article using [http://enos.itcollege.ee/~edmund/materials/viki-artikkel/Assessment-model-for-the-wiki-article.html the following assessment model].

==Summary==
Besides a short overview, what was discussed in this article, it should also include the author's own opinion about the topic.

==Category==
Add the following category to the end of the article (last row): 
'''<nowiki>[[Category:Operatsioonisüsteemide administreerimine ja sidumine]]</nowiki>'''

=Chosen topics=
Please write here your topic and name, group:
* '''Basic Automation with Python'''; Ardi Vaba; CSE-11
==Ideas==
* UNIX CLI password manager https://www.passwordstore.org and its GUI http://qtpass.org/

=References=
* [https://wiki.itcollege.ee/index.php/Osadmin_referaadi_teemad counterpart article in Estonian]
* http://manpage.io
* https://linuxjourney.com/
* [https://linux.die.net/man/ Linux man-pages]
* [https://linux.die.net Linux docs]
* http://www.tecmint.com/60-commands-of-linux-a-guide-from-newbies-to-system-administrator/
* http://www.tecmint.com/useful-linux-commands-for-system-administrators/
* http://www.cyberciti.biz/tips/top-linux-monitoring-tools.html
* http://www.thegeekstuff.com/2010/12/50-unix-linux-sysadmin-tutorials

[[Category:Operatsioonisüsteemide administreerimine ja sidumine]]

OSadmin wiki article

2017-01-30T10:47:36Z

Avaba: /* Chosen topics */

=Intro=
*Choose a topic from personal experience related with the subject or from topics found on the wiki page
*[[#Chosen_topics|Write the topic here]].
*Lecturer will confirm the topic
*Write your article in wiki environment
*Inform the [[Operating_systems#Lecturer|lecturer]] when the article is finished
*Receive feedback for corrections

=Requirements for the wiki article=
Author: name, group and date when the article is written

==Introduction ==
Covers points what will be discussed in the article, what are the requirements for the article reader; what are the operating system’s requirements.

==Contents==
All commands should be easily separable from the overall text.
Users should be able to copy the commands directly (additional info like prompt and user distinction symbols should be left out from the command description area)
The text should determine what user permissions are needed to perform these tasks.
The reader of your article is your fellow students, so try to avoid irrelevant information and stay on topic (don’t explain the meaning of IP address or how to install Ubuntu, when your topic is actually about htop)
All the content should be referenced.
Do not use slang and try to be grammatically correct. 

Bear in mind that this is an open environment, so everything you write in your wiki article, will be public. 

==Referencing==
Best practises of wiki referencing should be used.
Terms are but between square brackets to reference other articles in the system.
All drawing and images have to be referenced below the picture and in the text. (for example “System architecture can be viewed on image x, y and z.”)
Author’s own ideas have to be clearly presentable. Everything used from the sources have to be referenced.

==Fellow student review==
Please find a fellow student who will review your article and give a feedback on the discussion tab of the article using [http://enos.itcollege.ee/~edmund/materials/viki-artikkel/Assessment-model-for-the-wiki-article.html the following assessment model].

==Summary==
Besides a short overview, what was discussed in this article, it should also include the author's own opinion about the topic.

==Category==
Add the following category to the end of the article (last row): 
'''<nowiki>[[Category:Operatsioonisüsteemide administreerimine ja sidumine]]</nowiki>'''

=Chosen topics=
Please write here your topic and name, group:
* '''Automation with Python'''; Ardi Vaba; CSE-11
==Ideas==
* UNIX CLI password manager https://www.passwordstore.org and its GUI http://qtpass.org/

=References=
* [https://wiki.itcollege.ee/index.php/Osadmin_referaadi_teemad counterpart article in Estonian]
* http://manpage.io
* https://linuxjourney.com/
* [https://linux.die.net/man/ Linux man-pages]
* [https://linux.die.net Linux docs]
* http://www.tecmint.com/60-commands-of-linux-a-guide-from-newbies-to-system-administrator/
* http://www.tecmint.com/useful-linux-commands-for-system-administrators/
* http://www.cyberciti.biz/tips/top-linux-monitoring-tools.html
* http://www.thegeekstuff.com/2010/12/50-unix-linux-sysadmin-tutorials

[[Category:Operatsioonisüsteemide administreerimine ja sidumine]]

OSadmin wiki article

2017-01-30T10:47:12Z

Avaba: /* Chosen topics */

=Intro=
*Choose a topic from personal experience related with the subject or from topics found on the wiki page
*[[#Chosen_topics|Write the topic here]].
*Lecturer will confirm the topic
*Write your article in wiki environment
*Inform the [[Operating_systems#Lecturer|lecturer]] when the article is finished
*Receive feedback for corrections

=Requirements for the wiki article=
Author: name, group and date when the article is written

==Introduction ==
Covers points what will be discussed in the article, what are the requirements for the article reader; what are the operating system’s requirements.

==Contents==
All commands should be easily separable from the overall text.
Users should be able to copy the commands directly (additional info like prompt and user distinction symbols should be left out from the command description area)
The text should determine what user permissions are needed to perform these tasks.
The reader of your article is your fellow students, so try to avoid irrelevant information and stay on topic (don’t explain the meaning of IP address or how to install Ubuntu, when your topic is actually about htop)
All the content should be referenced.
Do not use slang and try to be grammatically correct. 

Bear in mind that this is an open environment, so everything you write in your wiki article, will be public. 

==Referencing==
Best practises of wiki referencing should be used.
Terms are but between square brackets to reference other articles in the system.
All drawing and images have to be referenced below the picture and in the text. (for example “System architecture can be viewed on image x, y and z.”)
Author’s own ideas have to be clearly presentable. Everything used from the sources have to be referenced.

==Fellow student review==
Please find a fellow student who will review your article and give a feedback on the discussion tab of the article using [http://enos.itcollege.ee/~edmund/materials/viki-artikkel/Assessment-model-for-the-wiki-article.html the following assessment model].

==Summary==
Besides a short overview, what was discussed in this article, it should also include the author's own opinion about the topic.

==Category==
Add the following category to the end of the article (last row): 
'''<nowiki>[[Category:Operatsioonisüsteemide administreerimine ja sidumine]]</nowiki>'''

=Chosen topics=
Please write here your topic and name, group:
* Automation with Python; Ardi Vaba; CSE-11
==Ideas==
* UNIX CLI password manager https://www.passwordstore.org and its GUI http://qtpass.org/

=References=
* [https://wiki.itcollege.ee/index.php/Osadmin_referaadi_teemad counterpart article in Estonian]
* http://manpage.io
* https://linuxjourney.com/
* [https://linux.die.net/man/ Linux man-pages]
* [https://linux.die.net Linux docs]
* http://www.tecmint.com/60-commands-of-linux-a-guide-from-newbies-to-system-administrator/
* http://www.tecmint.com/useful-linux-commands-for-system-administrators/
* http://www.cyberciti.biz/tips/top-linux-monitoring-tools.html
* http://www.thegeekstuff.com/2010/12/50-unix-linux-sysadmin-tutorials

[[Category:Operatsioonisüsteemide administreerimine ja sidumine]]