MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Responsiveness",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "47": {
                "pageid": 47,
                "ns": 0,
                "title": "Released Version",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[category:download]]\n{{DownloadNavigation}}\n\n{{Info|If you know what you want/need, you can go directly to [http://download.opensuse.org/ http://download.opensuse.org/]. \n\nIf you are not sure, please read the article below. }}\n{{Released_Version_Translations}}\n\n<br>\n\n=Choose the Installation Type=\n\n{{DownloadInstallType}}\n\n=Choose the Architecture=\n\n{{DownloadArch}}\n\n=Choose the Download Protocol=\n\n{{DownloadProtocol}}\n\n<!-- =Jigdo=\n[[Creating Jigsaw Download Images for DVD and CD Sets|You can also use Jigdo]]-->\n\n= Downloads =\n'''BEFORE YOU INSTALL READ THIS:''' You probably want to read about the [[Bugs:Most_Annoying_Bugs_10.2|Most Annoying Bugs]].\n\n{{Download_Released_Version_Table|10.2|GM|i386|x86_64|ppc}}\n\n* [http://download.opensuse.org/distribution/10.2/iso/cd/openSUSE-10.2-GM-i386-mini.iso Net-install ISO ]\n* [http://download.opensuse.org/distribution/10.2/iso/dvd/openSUSE-10.2-GM-LiveDVD.iso Live-DVD]\n* [[Mirrors_Released_Version|Mirrors Released Version]]\n* [[Additional YaST Package Repositories]]\n\n=Further Information=\n\n{{DownloadHelp}}"
                    }
                ]
            },
            "2197": {
                "pageid": 2197,
                "ns": 0,
                "title": "Remote Access to SUSE",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[Category:Networking]]\n[[Category:Remote Access]]\n= Introduction =\n== Purpose ==\n\n'''This paper is designed to help you setup the remote access solution that best fits your needs'''\n\nLike many people, you are reading this page looking for \nhelp on connecting to your SUSE Linux box via the network.\n\nThere are many ways to do this.\n\nYou may have a specific need which you (and I) hope this paper will help\nimplement a solution for.  Or you may not know enough about the\navailable solutions to decide what best fits your needs.  \n\nTherefore this paper must start with a discussion on the diferent types of remote access methods.  As a reader you are expected to choose the method that most closely meets your needs.  Then you can go to the implementation section to see how to set it up!\n\nPlease read the security section to evaluate your security needs.  Allowing remote access to a machine is literally '''inviting people to connect to your machine via the network'''.  Security is the only way to keep the thieves out.\n\nOkay, let's get started...\n\n== What is meant by Remote Access ==\n\nBy Remote access we really mean \n\"'''Running programs on your SUSE Linux box while you sit in front of another machine'''\".  \n\nNow \"'''Running programs on your SUSE box'''\" could be done in a shell, or may require a full GUI environment. \"'''while you sit in front of another machine'''\" implies that you already have a running network, correctly setup, with TCP/IP communication between the 2 machines working.\n\nThat is a prerequisite. This paper will not help you set up your network.\n\n== Different Remote Access Requirements ==\n\n\nSo you got at least 2 computers.  \nOne of them is a SUSE Linux (we'll call it \"Server\").  \nAnd from the other \"client\" computer you want to run programs on \"Server\".\n\nWell let's start by listing the possible ways:\n\nMaybe all you need is a \"'''Remote Shell'''\" on \"Server\".  That is easy.   But sometimes a shell is not enough. You may need to run a GUI (X-Windows) program remotely.  There are several ways to do this.  Each method fullfills different needs. Each method has it's advantages and disadvanteges.  But in general the methods to execute GUI programs fall into the following categories:\n\n- '''Running Individual GUI Programs''' from a remote shell. (ssh -X)  This method is secure.  This method is simple to use\n\n- '''X-Windows Remote''', where (on \"client\") you log into a remote machine (\"Server\"), instead of logging into your local machine.  This method uses your local X-Windows system (on \"Client\") as display.  As this method is not secure, it should only be used\n\n- '''Terminal Services''', where many people start virtual displays on \"Server\".  Each \"Virtual Display\" works independantly, but any number of them can run simultaneously on \"Server\".  This is similar to the Windows Terminal Service (hence the name). Here we don't need a local x-windows on \"client\".\n\n- '''Desktop Sharing''' is where you can remotetly see and use another existing session.  This allows for a shared session where what is done can be seen both localy and remotely.  This is mainly used for helping out other people while talking to them over the phone.\n\n- And lastly, you can execute programs on \"Server\" without user intervention.  This is used in shell scripts on the clients.  I call this \"'''Remote Program Submision'''\".  This method is different from the preveous methods in that a different method for indetification / authorization is required.  Specifically, one that does not have the user type a password.  The second difference is that I don't do this often, and thereby probably need help writing the document...\n\nIf your requirements fall into one of the above, then read on!\n\n== Remote Access and Security Requirements ==\n\nA very important requirement you need to consider is security.  Here we can break security into 3 parts:\n\n=== Authentication ===\n\nThe first security requirement is authentication.  That is verifying that the person asking for a remote connection is actually the person he says he is.\n\nThe methods used in this paper do this by requiring the user to identify himself with his username, and verifying it with a password known only to that user.\n\nThis is a common scheeme, used many times.  The difference is that this time \n'''It's not a joke'''.  This is not one of those places where you can use the password \"welcome\", or any of the other \"easy to remember\" passwords (such as the name of your pet!).\n\nThis is also not the place to use a password which you have preveously used in a mailling list, or as the password to your email account.\n\nIn general, you need to group your passwords into categories:\n\n'''Open Passwords''':   Yahoo mail, Google account, Mailing lists, etc\n\n'''Secure Passwords''': Passwords you use in a secure way with 3rd parties.\n\nBy allowing remote connctions to you machine, you move your computer password from the first category to the second category.  \n\n\nOn the internet there are people constantly trying to guess your password to break into your machine.  These attempts use a list of \"easy to remember\" passwords.  The number of machines that have be broken into with this simple method is astonishing!  I do not want to help you get on that list! So, '''Please take this warning seriously'''...\n\n=== Authorization ===\n\nThe second requirement is authorization.  Now that we've verified who is on the other side of the line, is he allowed to do this?\n\n\n=== Encryption ===\n\nAnd last, but in no way least, comes encryption.  The Internet is basically insecure.  With the event of WLANs, most home networks are also Insecure!  So you need to realize when it's possible for outsiders to spy on your remote connections.  \n\nPlease considder this seriously, as with many of these methods a third person could easily read your bank account number, Username and even your password, giving him all he needs to financially ruin you!\n\n\n=== Installing SSH Security ===\n\nIn this document SSH (configured for username / password checking) is used for all 3 security needs.  It is simple to setup, and secure.  But only as your passwords are :-)\n\n==== SSH Configuration ====\nThe following changes need to be made for SSH:\n\n===== Create User Group for Authorization =====\n\nCreate Group \u201cremotessh\u201d,\nAdd users that are allowed remote access to the group.\n\n\n===== Use User Group For Authorization =====\n\nIn file /etc/ssh/sshd_config add the following lines to bottom of file:\n   #\n   # OpenSUSE wiki Configuration\n   #\n   Port\t\t\t26\n   AllowGroups\t\tremotessh\n   GatewayPorts\t\tyes\n   X11DisplayOffset\t50\n   X11Forwarding\t\tyes\n\n===== Restart SSHD =====\nrestart ssh server with: \u201crcsshd restart\u201d\n\n\n===== SSH Client Configuration =====\n\nIn order that your clients use the new port 26\nyou need to change the  file /etc/ssh/ssh_config\nAdd lines:\n\n   ForwardAgent\t\tyes\n   ForwardX11\t\tyes\n\nThen for each known host with alternate port add following lines '''before''' \u201cHost *\u201d line:\n\n   Host\tjerry.westrick.com\n     Port 26\n\n= To Here...  Rest is not structured correctly =\n\n=== Remote Shell ===\n=== Remote Individual GUI Program ===\n=== X-Remote ===\n=== Terminal Services ===\nVNC and NxServer can create a \"Virtual\" GraphicCard, Keyboard, and Mouse on server.  In this form you can start as many \"Virtual Sessions\" as \"Server\" has resources to handle.  This allows multiple persons to work on \"Server\" simultaneously (using his/her local keyboard/mouse/screen ) without needing X-Windows running on the client.  This is similar to the windows \"'''Terminal Server'''\" functionality.\n\n=== Remote Desktop Sharing ===\n\nVNC can also copy the contents of the physical Graphic Card giving access to the real screen on \"Server\" (Remote Desktop).  Since you got access to the Physical screen, both the remote and the local users share this session and can see what the other is doing.  That is why these methods are used for remote support, and called \"'''Remote Desktop Sharing'''\".\n\n\n=== Remote Program Submision ===\n\n= Different methods =\n= Security =\n== Remote Shell ==\n== Remote X ==\n=== Remote X Login ===\n=== SSH -X ===\n== VNC ==\n\nSo what is VNC?\n\nVNC gives you a window on the client in which a remote session is running on the server, which for all practical purposes is equivalent to sitting at \"Server\" and using the Monitor/Keyboard/Mouse there.\n\nVNC can use a \"Virtual\" GraphicCard, Keyboard, and Mouse on server.  In this form you can start as many \"Virtual Sessions\" as \"Server\" has resources to handle.  This allows multiple persons to work on \"Server\" simultaneously (using his/her local keyboard/mouse/screen ).  This is similar to the windows \"'''Terminal Server'''\" function.\n\nVNC can also copy the contents of the real Graphic Card giving access to the real screen on \"Server\" (Remote Desktop).  Since you got access to the Physical screen, both the remote and the local users share this session and can see what the other is doing.  That is why these methods are used for remote support, and called \"'''Remote Desktop Sharing'''\".\n\nAs you can see VNC is very flexible, and therefor has lots of options each suited for diferent needs.  Infact you can even \"Remote Desktop\" share a VNC Terminal Session, by combing 2 of the methods together! \n\n\n=== VNC as Terminal Server ===\n\n==== VNC Remote X Login ====\n\nHere we use a VNC setup designed to use minimal resources on the server.\nThis is done by not starting the VNC session until someone tries to connect, and shutting the VNC session down as soon as client disconnects from it.\n\nThe VNC sessions are identical to the sessions on the physical screen of \"Server\", they even start of with the identical logon screen.\n\n \n==== VNC User Sessions ====\n\nHere we \"Prestart\" vnc sessions for specific users, therefore no login screen is presented.  This uses more resources as the VNC Session is running even when no client is connected to the session watching it.  But there in lies it's advantage, \"watching a session\" and \"using a session\" are not the same thing!  This method is very usefull for starting long running programs before going home.  Once home you can re-connect to the session and see how things are going.\n\n\n=== VNC as Remote Desktop Sharing ===\n\n==== Sharing a Users Session ====\n\nHere VNC is used to \"Share\" the current user's Desktop.  This is most used for Remote Support, and is provided by KDE directly.\n\n\n==== Sharing the local X-Windows Session ====\n\nHere we setup vnc to allow remote access directly to the physical graphic card (X-Windows system), allowing us to see / use the real screen on \"Server\".  This is most used in support where operators do not want 2 people working on the same machine at the same time.  In this method the person physically at server can watch everything the remote user is doing.\n\nNOTE: (the windows version of VNC server only supports this mode, as windows does not support virtual screens)\n\n== NxServer =="
                    }
                ]
            }
        }
    }
}