X2Go Bug report logs - #176
x2gobroker: error 405 when accessing /pubkeys/

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#176: X2Go issue #176 (src:x2gobroker) has been marked as closed
Reply-To: tag@ymir, 0.0.1.1@ymir, 176-quiet@bugs.x2go.org
Resent-To: Anders Bruun Olsen <abo@dsl.dk>
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 23 Apr 2013 19:57:40 +0000
Resent-Message-ID: <handler.176.U176.13667470068502@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: report 176
X-X2Go-PR-Package: x2gobroker
X-X2Go-PR-Keywords: pending
Received: via spool by 176-submitter@bugs.x2go.org id=U176.13667470068502
          (code U ref 176); Tue, 23 Apr 2013 19:57:40 +0000
Received: (at 176-submitter) by bugs.x2go.org; 23 Apr 2013 19:56:46 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.2 required=5.0 tests=FH_FROMEML_NOTLD,NO_RELAYS,
	URIBL_BLOCKED autolearn=no version=3.3.2
Received: by ymir (Postfix, from userid 1005)
	id F03335DB2D; Tue, 23 Apr 2013 21:56:21 +0200 (CEST)
From: tag@ymir, 0.0.1.1@ymir
To: 176-submitter@bugs.x2go.org
Cc: control@bugs.x2go.org, 176@bugs.x2go.org
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Message-Id: <20130423195621.F03335DB2D@ymir>
Date: Tue, 23 Apr 2013 21:56:21 +0200 (CEST)

close #176
thanks

Hello,

we are very hopeful that X2Go issue #176 reported by you
has been resolved in the new release (0.0.1.1) of the
X2Go source project »src:x2gobroker«.

You can view the complete changelog entry of src:x2gobroker (0.0.1.1)
below, and you can use the following link to view all the code changes
between this and the last release of src:x2gobroker.

    http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=4085176be6f5895c931e34e6549ea9849e13ca0b;hp=7a77058f345af93356c9615df70c92644fa98549

If you feel that the issue has not been resolved satisfyingly, feel
free to reopen this bug report or submit a follow-up report with
further observations described based on the new released version
of src:x2gobroker.

Thanks a lot for contributing to X2Go!!!

light+love
X2Go Git Admin (on behalf of sender of this mail)

---
X2Go Component: src:x2gobroker
Version: 0.0.1.1
Status: RELEASE
Date: Tue, 23 Apr 2013 21:38:07 +0200
Fixes: 154 170 171 172 175 176 180
Changes: 
 x2gobroker (0.0.1.1) RELEASED; urgency=low
 .
   * New upstream version (0.0.1.1):
     - Add WSGI support to X2Go Session Broker. Allows plugging into
       Apache2 by using the mod_wsgi module.
     - Add Apache2 configuration for WSGI support that shows how to
       setup a VirtualHost for X2Go Session Broker.
     - For sessions profiles with autologin enable, add a dummy key
       session profile parameter that triggers key based auth in X2Go Client.
       (Fixes: #154).
     - Fix hard-coded path to x2gobroker's authservice socket.
     - Separate logging logic of x2gobroker-authservice from the rest of
       the logging in x2gobroker. (Fixes: #172).
     - x2gobroker-pubkeyauthorizer: no logging-to-file support anymore.
       (Fixes: #175).
     - Fix name of get() method for /pubkeys/ URL path. (Fixes: #176).
     - Move AuthService server code fully into x2gobroker-authservice
       daemon script.
     - Add forgotten file: x2gobroker-authservice-logger.conf. (Fixes: #180).
     - Add script: x2gobroker-testauth.
     - Add enable()/disable() methods to broker backends.
     - Move complete authservice logic into x2gobroker-authservice script.
     - Add command and directrdp session profile parameters to defaults.
     - Fix wrong usage of session option »cmd«, has to be »command«.
   * /debian/control:
     + Fix --root parameter in DEB_PYTHON_INSTALL_ARGS.
     + Let bin:package x2gobroker-authservice depend on python-x2gobroker (of the
       same version). (Fixes: #170).
   * Properly remove the X2Go Session broker log files on package purgal.
   * Let bin:package x2gobroker-authservice create x2gouser:x2gouser, as well.
     (Fixes: #171).

Send a report that this bug log contains spam.