Eduroam
The DIAS is connected to eduroam.
We are both acting as a Service Provider and as an Identity Provider.
We follow as closely as possible the Eduroam Policy
Technical details
- SSID: eduroam (all lower case)
- Encryption: WPA2
- EAP Method: TTLS
- Phase-2 authentication: PAP
- CA=certificate from below
- Identity=USERNAME@SCHOOL.dias.ie
- Anonymous Identity=
- Password=your_dias_password
Validity
Not Before: Dec 15 11:09:20 2016 GMT
Not After : Dec 13 11:09:20 2026 GMT
Same file, with other extensions
Remote access
- Just visit webmail.dias.ie.
dias – Institute for Advanced Studies Act date? - lewis.stp.dias.ie in the case of STP/SCS
- ariadne.dias.ie in the case of CP
Webmail
SSH
External access can be done via SSH
SSH clients are standard components of Unix, Linux and MacOS X, and free clients such as Putty exist for MS Windows.
When logging in, before you give your username and password details, you need some proof that the remote machine is what it claims to be. Typically, the client presents you with a cryptographic fingerprint of the actual remote machine, and ask you to accept or reject it. Here is the list of the valid fingerprints
| Computer | lewis.stp.dias.ie |
| IPv4 | 160.6.133.9 |
| IPv6 | 2001:770:60:85::9 |
| RSA key fingerprint | ea:5b:f6:23:10:44:60:5c:2d:f2:f7:f7:82:12:2b:3e |
| ECDSA key fingerprint | SHA256:5pD+ZDMI/jksw6e10JwNvumfwtO49AYyB0NdSVePy4c 87:2a:44:23:7f:23:09:be:3a:86:3e:ef:fc:ff:48:3c |
| ssh -o HostKeyAlgorithms=ssh-rsa -o VisualHostKey=yes lewis.stp.dias.ie |
+--[ RSA 2048]----+ | .o+o. | | .o o . | | + . | | o . | | oS. | | ... . . | | ..oo o . | | .Eo+.o . . | | .++ o.. . | +-----------------+
|
| ssh -o HostKeyAlgorithms=ecdsa-sha2-nistp256 -o VisualHostKey=yes lewis.stp.dias.ie |
+--[ECDSA 256]---+ | | | | | o o | | . = o . | | . = o S . | | o o.o . | |. . . .E | |o+. .. o | |+o++...o.. | +-----------------+
|
| Computer | ariadne.dias.ie |
| IPv4 | 160.6.1.45 |
| IPv6 | 2001:770:60:1::45 |
| RSA 2048bits key fingerprint | 58:d2:fa:b2:c7:6a:04:4d:3a:71:fa:73:a6:2c:6c:7a |
| ECDSA 256bits key fingerprint | SHA256:Q/JTth6gCbFBKrv9fxYNUtOe6oHiHSl7ezj3geynVhA 79:3a:59:b1:3d:c8:5f:19:2d:de:0e:1e:10:10:ed:15 |
| ssh -o HostKeyAlgorithms=ssh-rsa -o VisualHostKey=yes ariadne.dias.ie |
+--[ RSA 2048]----+ | | | . o. | | B. o | | = .= | | +o S | | +.o | | . o.*. | | E +oo | | .+ ooo | +-----------------+
|
| ssh -o HostKeyAlgorithms=ecdsa-sha2-nistp256 -o VisualHostKey=yes ariadne.dias.ie |
+--[ECDSA 256]---+ | o+. E. | | .... | | ....o .| | o =.o = | | S * o * .| | = . + + | | + . . .| | . | | | +-----------------+
|
Simple Finance System
Current version: 0.2
Last update: October 2011
Licence: GPLv2 or later
Simple Finance System
Download
Download available from GitHub
How it works
Description and features
A few snapshots
| {slimbox images/stories/admin/Simple-Finance-System/snapshots/01-login.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/01-login.png.jpg,01-login} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/02-main-menu.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/02-main-menu.png.jpg,02-main-menu} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/03-creating-a-travel-request.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/03-creating-a-travel-request.png.jpg,03-creating-a-travel-request} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/04-editing-a-travel-request-1.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/04-editing-a-travel-request-1.png.jpg,04-editing-a-travel-request-1} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/05-editing-a-travel-request-2-items-type.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/05-editing-a-travel-request-2-items-type.png.jpg,05-editing-a-travel-request-2-items-type} | |||||
| {slimbox images/stories/admin/Simple-Finance-System/snapshots/06-editing-a-travel-request-3-exchange-rate.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/06-editing-a-travel-request-3-exchange-rate.png.jpg,06-editing-a-travel-request-3-exchange-rate} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/07-getting-approval-for-a-travel-request-1.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/07-getting-approval-for-a-travel-request-1.png.jpg,07-getting-approval-for-a-travel-request-1} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/08-getting-approval-for-a-travel-request-2.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/08-getting-approval-for-a-travel-request-2.png.jpg,08-getting-approval-for-a-travel-request-2} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/09-travel-request-list.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/09-travel-request-list.png.jpg,09-travel-request-list} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/10-travel-request-closed-and-linked.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/10-travel-request-closed-and-linked.png.jpg,10-travel-request-closed-and-linked} | |||||
| {slimbox images/stories/admin/Simple-Finance-System/snapshots/11-creating-an-expense-report.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/11-creating-an-expense-report.png.jpg,11-creating-an-expense-report} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/12-expense-report-linked.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/12-expense-report-linked.png.jpg,12-expense-report-linked} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/13-new-purchase-order.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/13-new-purchase-order.png.jpg,13-new-purchase-order} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/14-editing-purchase-order.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/14-editing-purchase-order.png.jpg,14-editing-purchase-order} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/15-finance-main-menu.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/15-finance-main-menu.png.jpg,15-finance-main-menu} | |||||
| {slimbox images/stories/admin/Simple-Finance-System/snapshots/16-finance-po-list.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/16-finance-po-list.png.jpg,16-finance-po-list} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/17-finance-tr-list.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/17-finance-tr-list.png.jpg,17-finance-tr-list} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/18-finance-er-list.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/18-finance-er-list.png.jpg,18-finance-er-list} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/19-finance-section-management.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/19-finance-section-management.png.jpg,19-finance-section-management} | {slimbox images/stories/admin/Simple-Finance-System/snapshots/20-finance-supplier-management.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/20-finance-supplier-management.png.jpg,20-finance-supplier-management} | |||||
| {slimbox images/stories/admin/Simple-Finance-System/snapshots/21-finance-log-exemple.png.jpg,images/stories/admin/Simple-Finance-System/thumbs/21-finance-log-exemple.png.jpg,21-finance-log-exemple} |
Origin
The finance system was initialy based on AssetMan
Developments
DIAS uses a number of open source software and sometimes gives back to the community.
Leaving User
Policy on closure of accounts for people leaving DIAS
- This policy is intended to cover staff and scholars who leave the Institute on retirement, or to take up alternative employment, or as a result of their contracts expiring. Research associates, holders of honorary appointments and others who are engaged in on-going collaborative research with Institute staff will continue to be regarded as active staff members and are not covered by this policy.
- People who are about to leave DIAS should discuss, in consultation with the IT staff and where appropriate with their head of section or supervisor, which files they wish to take with them, which may be deleted, and which should be transferred to another user. This should be decided at least one month in advance of the scheduled departure date. In some cases, and subject to procedures laid down by the finance office, it may be possible for individuals to purchase their institute laptops at residual inventory value to take with them.
- Unless other arrangements are agreed, and approved by the relevant head of section, the IT staff will proceed as follows.
- The user’s account(s) will be kept open for remote access for a mutually agreed period, normally one month, post departure and then closed down.
- The user’s institute mailbox will be set to forward to a new address nominated by the departing individual for a period of six months. The following automated message will be sent to the sender of any forwarded messages: “This address is no longer in use and your message has been forwarded to new address Please update your address-book and use this for all future correspondence.”
About IT
Welcome to the IT Section of The Dublin Institute for Advanced Studies
You will find in this section some useful information about your visit within DIAS.
We are also IPv6-enabled and certified by INEX
Acceptable Usage Policy
Scope and Purpose of Code
The purpose of this code is to establish general regulations governing the use of Information Technology (IT) resources within the Institute and to define the rights and responsibilities of users. The IT infrastructure provides an essential part of our working environment and represents a significant investment by the Institute and it must be used with care and with consideration for others. If misused there is a risk of actions, deliberate or not, that are harmful in various ways including (a) interference with the rights of others (b) violation of the law (c) interference with the research activities of the Institute (d) endangering the integrity of the Institute’s computer network.
The code applies to all persons authorised to use the Institute’s IT resources. Users are also required to comply with the acceptable use policy of HEAnet, the Institute’s primary internet service provider. A copy of the HEAnet acceptable use policy is attached to and forms part of this code of conduct.
Nothing in this document attempts or should be interpreted in a manner that attempts to limit academic freedom.
Link: HEAnet’s acceptable use policy
Access
Access to IT resources will normally be given with the assistance of the Institute’s IT staff and and will typically involve the allocation of an individual password. The integrity of the password system is the primary defence against breaches of computer security and it must be treated accordingly. Users should not divulge their password to any other person and are responsible for keeping it secret. In particular it should not be written down in an obvious place, nor transmitted over insecure channels (eg in non-encrypted form) and users should as far as possible avoid re-using the same password for access to non-Institute sites. The IT staff should be consulted if there is any doubt over what constitutes safe and unsafe behaviour. Users will typically be held personally responsible for all activities carried out under their username.
Acceptable Use
Internet, e-mail and other IT systems are provided as part of the general research environment of the Institute and its constituent schools and to help staff in the performance of their duties. Occasional personal use of these facilities is permissible, but should be kept to a minimum and must not be such as to bring the Institute into disrepute. Any use of the Institute’s IT facilities for personal commercial purposes is strictly forbidden.
Any software or hardware which could significantly affect other users, or interact with the system in a nontrivial fashion, or require changes to global system parameters or libraries, may only be installed by the IT support staff.
No person should deliberately or through carelessness jeopardize the integrity, performance or reliability of the Institute’s computer equipment, software and other IT systems, nor selfishly seek to monopolise shared system resources to the detriment of other users.
Users must not seek to intercept network traffic, files or data to which they are not entitled.
The use of IT facilities is subject to an evolving set of both Irish and European Laws and users are expected to use the Institute’s facilities in a manner compliant with these laws. If a user is unsure of whether something is covered by law they should consult the IT staff. The Institute’s IT staff are responsible for ensuring that the Institute’s IT systems are fully compliant with software license requirements. All users are required to support them in this. Users are however responsible for ensuring that their own activities and uses of the IT facilities are in compliance with both Irish and European Law.
Monitoring and privacy
In general the Institute undertakes as far as possible to respect the privacy of personal files and e-mail. Technical support staff are forbidden to examine the contents of a user’s communications and files out of mere curiosity or at the arbitrary behest of any individual.
While the Institute does not deliberately seek to monitor the activities of users of the IT system, users should be aware that many details are automatically captured in system logs. Also in exceptional circumstances where it is necessary for the protection of staff and visitors, or where there is a strong suspicion of abuse, or where it is a legal requirement, or where it is necessary for system security (eg after a virus attack), the Institute may monitor the use of IT facilities and examine a user’s personal files. When it is found necessary to examine any personal files in an intrusive manner the user will be informed.
Violations of Code
Violations of this policy will result in disciplinary action and could also result in legal action. Users should report any misuse of the Institute’s IT systems to the Director of the School concerned or the Registrar’s office and, where appropriate, also inform local IT support staff.
This AUP was adopted by the Computer Committee, 14 October 2003
Information for Visitors
Presentations
The following equipment can be provided:
- an overhead projector
- an LCD projector for computer display
- a laptop PC
However, to avoid any last-minute surprises, let us know in advance:
- what software you’ll need
- what/when your presentation is
- how you’ll transfer the presentation if you’re using the laptop
Bringing a Laptop (… and your adapter for UK plugs, please!)
If so configured, your laptop will auto-discover the network settings (i.e. DHCP).
If this isn’t the case, or if it doesn’t work, please contact the administrator (Room 302, extension 132) and ask for help.
Bringing files
We suggest bringing files on USB flash disk, or pulling them directly across the Internet once you arrive.
17th November @ 8pm – #DIASDublin School of Celtic Studies Statutory Public Lecture 2017 taking place @tcddublin
DIAS Giovanna Tinetti Lecture "Brave new worlds: the planets in our galaxy" youtu.be/le0Kh0JxMMA via @YouTube
If you missed the recent #DIASDublin talk by Prof Giovanna Tinetti @UCL_CPS you can watch it here : dias.ie/2014/11/24/dia…
Digital images of this can also be viewed on Irish Script on Screen @SCSLibrary isos.dias.ie twitter.com/Library_RIA/st…

















