<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.ulyssis.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Robin5210</id>
	<title>ULYSSIS documentation - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.ulyssis.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Robin5210"/>
	<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/Special:Contributions/Robin5210"/>
	<updated>2026-05-08T10:58:50Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.15</generator>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Talk:Keeping_your_website_secure&amp;diff=218</id>
		<title>Talk:Keeping your website secure</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Talk:Keeping_your_website_secure&amp;diff=218"/>
		<updated>2015-01-28T15:30:47Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;kies een goed wachtwoord, dit is een sql-injectie+doe dus een prepared statement, update uw stuff, laat geen oude rommel rondslingeren, gebruik captcha's, da soort shit&lt;br /&gt;
&lt;br /&gt;
There are many aspects to keeping your website secure.&lt;br /&gt;
&lt;br /&gt;
= Your password =&lt;br /&gt;
You have probably heard this ons numerous times. But we can't repeat it enough. Choose a good password containing letter, numbers and other characters. Don't choose something to obvious. &lt;br /&gt;
&lt;br /&gt;
When you think your password has been comprimised, don't change it immediately. First try to determine the source of your password leak and fix it. If the leak continous to exist, it's likely that your password will be compromised again in the future. When your password leak has been fixed, it's time to change it.&lt;br /&gt;
&lt;br /&gt;
= Updates =&lt;br /&gt;
Another key aspect of securing your site is keeping it up to date. If you are using a cms, use Google to search how to update it. If you wrote a custom website, lookout for updates for the libraries you used to create your website.&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Talk:Keeping_your_website_secure&amp;diff=217</id>
		<title>Talk:Keeping your website secure</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Talk:Keeping_your_website_secure&amp;diff=217"/>
		<updated>2015-01-28T14:51:15Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: Created page with &amp;quot;There are many aspects to keeping your website secure.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are many aspects to keeping your website secure.&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Setting_up_WordPress&amp;diff=97</id>
		<title>Setting up WordPress</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Setting_up_WordPress&amp;diff=97"/>
		<updated>2014-05-23T16:49:59Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: Created page with &amp;quot;==Wordpress installeren gaat zeker gemakkelijk op onze servers==  Je downloadt het installatiebestand van de [http://http://wordpress.org wordpress-site].  Hierbij krijg je ee...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Wordpress installeren gaat zeker gemakkelijk op onze servers==&lt;br /&gt;
&lt;br /&gt;
Je downloadt het installatiebestand van de [http://http://wordpress.org wordpress-site].&lt;br /&gt;
&lt;br /&gt;
Hierbij krijg je een gecomprimeerd bestand (.tar.gz of .zip) dit pak je uit.&lt;br /&gt;
&lt;br /&gt;
Je krijgt dan een map met bestanden, deze bestanden (en dus niet de map) kopieer je via filezilla of een ander ftp programma naar je www-map op je shellaccount.&lt;br /&gt;
&lt;br /&gt;
Hierna surf je naar je account, dus naar username.ulyssis.be, je krijgt hier een melding dat je je wp-config.php nog moet aanmaken, het gemakkelijkste is gewoon de wizard blijven volgen, klik dus op: ''Create a Configuration File''.&lt;br /&gt;
&lt;br /&gt;
Daarna op ''Let's go!'' waarna je gegevens van je database gaat moeten invullen:&lt;br /&gt;
&lt;br /&gt;
* '''Database Name: '''als je nog geen mysql database of user hebt aangemaakt op UCC dan moet je dat daar doen. De standaard database is dan: username_username.&lt;br /&gt;
* '''User Name: '''dit is de naam die je hebt opgegven tijdens het maken van je mysql account, vaak is deze hetzelfde als je gebruikersnaam bij ULYSSIS.&lt;br /&gt;
* '''Password: '''het wachtwoord dat je hebt opgegven bij de aanmaak van je mysql account&lt;br /&gt;
* '''Database Host: '''dit is &amp;lt;code&amp;gt;mysql.ulyssis.org&amp;lt;/code&amp;gt;&lt;br /&gt;
* Het laatste veld verander je niet.&lt;br /&gt;
&lt;br /&gt;
Vervolgens krijg je de volgende error: ''Sorry, but I can’t write the &amp;lt;code&amp;gt;wp-config.php&amp;lt;/code&amp;gt; file.'' Maar geen paniek, de tekst die WordPress gemaakt heeft is hetgene wat we nodig hebben. Kopieer deze tekst, sla dit op in een bestand &amp;lt;code&amp;gt;wp-config.php&amp;lt;/code&amp;gt;. Dit bestand zet je dan weer via Filezilla over naar je www-directory.&lt;br /&gt;
&lt;br /&gt;
Klik hierna op ''Run The install.'' Hier kan je dan de laatste gegevens invullen.&lt;br /&gt;
&lt;br /&gt;
Daarna zal de installatie zichzelf uitvoeren en voilà, je hebt wordpress geïnstalleerd.&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Mailbox&amp;diff=96</id>
		<title>Mailbox</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Mailbox&amp;diff=96"/>
		<updated>2014-05-23T14:21:30Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: Created page with &amp;quot;Your ulyssis account includes an email address: &amp;lt;code&amp;gt;''username''@ulyssis.org&amp;lt;/code&amp;gt;. It is important you check your ulyssis mail regularly, because all important information...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Your ulyssis account includes an email address: &amp;lt;code&amp;gt;''username''@ulyssis.org&amp;lt;/code&amp;gt;. It is important you check your ulyssis mail regularly, because all important information will be sent to this address. You can check your e-mail using the webmail or an email client of your own.&lt;br /&gt;
&lt;br /&gt;
==Webmail==&lt;br /&gt;
You can access your mail via a webinterface: https://webmail.ulyssis.org. Use your username and password to enter the website.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==POP and IMAP access==&lt;br /&gt;
You can access your ulyssis mail by POP or IMAP protocol. The configuration parameters are:&lt;br /&gt;
&lt;br /&gt;
* '''server''': mail.ulyssis.org&lt;br /&gt;
* '''username''': ''your username''&lt;br /&gt;
* '''security''': SSL&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Useful_Linux_Commands&amp;diff=86</id>
		<title>Useful Linux Commands</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Useful_Linux_Commands&amp;diff=86"/>
		<updated>2014-05-12T17:27:17Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Once you've connected, you can use these commands to use the ULYSSIS shell.&lt;br /&gt;
&lt;br /&gt;
First of all, whenever you need to type a longer command or filename, try the &amp;lt;code&amp;gt;TAB&amp;lt;/code&amp;gt; key as it will try to complete the name of the command or file you are typing. Pressing &amp;lt;code&amp;gt;TAB&amp;lt;/code&amp;gt; twice will show a list of possible completions.&lt;br /&gt;
&lt;br /&gt;
A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/.&lt;br /&gt;
&lt;br /&gt;
==Basic file managment==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cd directoryname&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with &amp;lt;code&amp;gt;cd ..&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ls&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
List the contents of the current directory. Many different formats are available, a common one is &amp;lt;code&amp;gt;ls -al&amp;lt;/code&amp;gt;. To accomodate MS-DOS/Windows users, &amp;lt;code&amp;gt;dir&amp;lt;/code&amp;gt; is an alias (synonym) for &amp;lt;code&amp;gt;ls -alF&amp;lt;/code&amp;gt;, which gives output similar to the &amp;lt;code&amp;gt;dir&amp;lt;/code&amp;gt; command in MS-DOS/Windows.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cp inputfile targetfile&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mv inputfile targetfile&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: &amp;lt;code&amp;gt;for i in *.htm; do mv i; done&amp;lt;/code&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;rm filename&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mkdir dirname&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Creates a directory called dirname.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;rmdir dirname&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). &lt;br /&gt;
&lt;br /&gt;
==Getting help==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;man command-name&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;apropos word&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Searches through headers of all man pages.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;help command-name&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays help about command-name. Only for internal bash-functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;bash&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc&lt;br /&gt;
&lt;br /&gt;
==Text editors==&lt;br /&gt;
&lt;br /&gt;
It's easier to use a text editor on a server, than editing your file locally and uploading that file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;pico&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;nano&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Probably the easiest text editor. Should be self-explanatory.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;joe&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Another easy text editor. Press Ctrl+C to quit.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;vim&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Probably the best text editor. Start editing by pressing &amp;lt;code&amp;gt;i&amp;lt;/code&amp;gt;. Stop editing by pressing the &amp;lt;code&amp;gt;escape&amp;lt;/code&amp;gt; key. Save and quit with &amp;lt;code&amp;gt;:wq&amp;lt;/code&amp;gt;. Quit without saving with &amp;lt;code&amp;gt;:q!&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Utilities==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;df&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch.&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;du&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals).&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;quota&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits.&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;ps&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication.&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;htop&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q').&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Useful_Linux_Commands&amp;diff=85</id>
		<title>Useful Linux Commands</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Useful_Linux_Commands&amp;diff=85"/>
		<updated>2014-05-12T17:26:00Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: Created page with &amp;quot;Once you've connected, you can use these commands to use the ULYSSIS shell.  First of all, whenever you need to type a longer command or filename, try the TAB key as it will t...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Once you've connected, you can use these commands to use the ULYSSIS shell.&lt;br /&gt;
&lt;br /&gt;
First of all, whenever you need to type a longer command or filename, try the TAB key as it will try to complete the name of the command or file you are typing. Pressing TAB twice will show a list of possible completions.&lt;br /&gt;
&lt;br /&gt;
A more extensive document on this can be found at http://info.ee.surrey.ac.uk/Teaching/Unix/.&lt;br /&gt;
&lt;br /&gt;
==Basic file managment==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cd directoryname&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Change directory. Works the same as under MS-DOS. cd without argument changes to your home directory (like My Documents in windows). Go to the parent directory with &amp;lt;code&amp;gt;cd ..&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ls&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
List the contents of the current directory. Many different formats are available, a common one is &amp;lt;code&amp;gt;ls -al&amp;lt;/code&amp;gt;. To accomodate MS-DOS/Windows users, &amp;lt;code&amp;gt;dir&amp;lt;/code&amp;gt; is an alias (synonym) for &amp;lt;code&amp;gt;ls -alF&amp;lt;/code&amp;gt;, which gives output similar to the &amp;lt;code&amp;gt;dir&amp;lt;/code&amp;gt; command in MS-DOS/Windows.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cp inputfile targetfile&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy inputfile to targetfile. Additional arguments (e.g. -r or -v are explained in the man-page.)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mv inputfile targetfile&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Move inputfile to targetfile. Additional arguments (e.g. -i or -v are explained in the man-page.) This is the way to rename a file. Note that you cannot use a construction like mv *.htm *.html to add an ``l'' to a bunch of files. A small shell script can provide a way to do this: &amp;lt;code&amp;gt;for i in *.htm; do mv i; done&amp;lt;/code&amp;gt;&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;rm filename&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Remove filename. Additional arguments (e.g. -r or -v are explained in the man-page.) Note: there is no undelete-alike function in most unices.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mkdir dirname&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Creates a directory called dirname.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;rmdir dirname&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Removes an empty directory. Use rm -r to delete a directory and recursively everything in it. Add -f to disable any prompts (dangerous!). &lt;br /&gt;
&lt;br /&gt;
==Getting help==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;man command-name&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays manual pages, if available. E.g. man ls. Use 'q' to exit. Relatives: apropos, help.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;apropos word&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Searches through headers of all man pages.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;help command-name&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays help about command-name. Only for internal bash-functions.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;bash&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The Bourne Again SHell. Widely used successor of sh, the Bourne shell. This is the program you're working under after you open a ssh-session (you don't have to start it to use it). Bash interprets your commands, and executes them. Tab-completion, * and ? expansions, etc are all bash functions. man bash will give you tons of info about it. Alternatives : tcsh, zsh, rc&lt;br /&gt;
&lt;br /&gt;
==Text editors==&lt;br /&gt;
&lt;br /&gt;
It's easier to use a text editor on a server, than editing your file locally and uploading that file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;pico&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;nano&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Probably the easiest text editor. Should be self-explanatory.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;joe&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Another easy text editor. Press Ctrl+C to quit.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;vim&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Probably the best text editor. Start editing by pressing &amp;lt;code&amp;gt;i&amp;lt;/code&amp;gt;. Stop editing by pressing the &amp;lt;code&amp;gt;escape&amp;lt;/code&amp;gt; key. Save and quit with &amp;lt;code&amp;gt;:wq&amp;lt;/code&amp;gt;. Quit without saving with &amp;lt;code&amp;gt;:q!&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
==Utilities==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;df&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about the free diskspace on the system. df . will give info about the filesystem where the current directory resides. The output becomes a bit more readable with the -h switch.&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;du&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about the diskusage in the current directory (and its subdirectories. A common parameter is -s , equivalent to -summarize , to summarize the disk-usage (without the per-subdir totals).&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;quota&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about your diskusage, and your disk quota. Quota are limits on diskusage, imposed by the system administrator. The system will warn you if you exceed these limits.&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;ps&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays info about processes. Various options possible, for example ps auxf gives info on all processes, including process owner, memory usage, and parent-child indication.&lt;br /&gt;
    &lt;br /&gt;
&amp;lt;code&amp;gt;htop&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Displays top CPU processes. Use it to see what gets most cpu power at the moment. Don't leave top open for a long time, since it eats cpu time itself. (quit with 'q').&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Transferring_your_account&amp;diff=83</id>
		<title>Transferring your account</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Transferring_your_account&amp;diff=83"/>
		<updated>2014-05-11T12:57:26Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KU Leuven Login. Otherwise the new webmaster can not accept the account transfer.&lt;br /&gt;
&lt;br /&gt;
The instructions below must be executed by the current account owner.&lt;br /&gt;
&lt;br /&gt;
* Login into [https://ucc.ulyssis.org/ UCC].&lt;br /&gt;
* Choose 'Transfer account' in the menu on the right.&lt;br /&gt;
* Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!)&lt;br /&gt;
&lt;br /&gt;
The new owner will get an email to confirm the transfer.&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Transferring_your_account&amp;diff=82</id>
		<title>Transferring your account</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Transferring_your_account&amp;diff=82"/>
		<updated>2014-05-11T12:57:00Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KULeuven Login. Otherwise the new webmaster can not accept the account transfer.&lt;br /&gt;
&lt;br /&gt;
The instructions below must be executed by the current account owner.&lt;br /&gt;
&lt;br /&gt;
* Login into [https://ucc.ulyssis.org/ UCC].&lt;br /&gt;
* Choose 'Transfer account' in the menu on the right.&lt;br /&gt;
* Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!)&lt;br /&gt;
&lt;br /&gt;
The new owner will get an email to confirm the transfer.&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
	<entry>
		<id>https://docs.ulyssis.org/index.php?title=Transferring_your_account&amp;diff=81</id>
		<title>Transferring your account</title>
		<link rel="alternate" type="text/html" href="https://docs.ulyssis.org/index.php?title=Transferring_your_account&amp;diff=81"/>
		<updated>2014-05-11T12:56:11Z</updated>

		<summary type="html">&lt;p&gt;Robin5210: Created page with &amp;quot;=Transferring your account=  You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KULeuven Login. Other...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Transferring your account=&lt;br /&gt;
&lt;br /&gt;
You can transfer the account of your (faculty) organization to a new webmaster. The new webmaster must have a valid Centrale KULeuven Login. Otherwise the new webmaster can not accept the account transfer.&lt;br /&gt;
&lt;br /&gt;
The instructions below must be executed by the current account owner.&lt;br /&gt;
&lt;br /&gt;
* Login into [https://ucc.ulyssis.org/ UCC].&lt;br /&gt;
* Choose 'Transfer account' in the menu on the right.&lt;br /&gt;
* Enter the details of the new account owner. (Make sure you type the KULeuven email address correct!)&lt;br /&gt;
&lt;br /&gt;
The new owner will get an email to confirm the transfer.&lt;/div&gt;</summary>
		<author><name>Robin5210</name></author>
	</entry>
</feed>