Custom Query (196 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (169 - 171 of 196)

Ticket Resolution Summary Owner Reporter
#35 fixed sql web interface should make the lockername+ prefix more obvious presbrey andersk
Description

(Imported from help.mit.edu #545970.)

andersk:

The SQL web interface should make it clear that it's going to prepend lockername+ to the database name. An easy solution would be

new database: andersk+[text box ] [add]

geofft:

I've added your suggestion to the live version in the locker (/mit/sql/web_scripts/main/tpl/main.php).

Joe, could you check this in to SVN? I don't seem to have access to the repository.

andersk:

This change has apparently gotten reverted, and users continue to be confused by it (such as stjerne who thought his database name was amanger, and me who keeps creating databases like hmmt+hmmt+database). Can this change be reapplied?

andersk:

What is the status of this sql.mit.edu UI bug? It was fixed and then reverted.

#48 fixed SNI, giving certificates on *.scripts.mit.edu for FF 2 and IE 7 presbrey andersk
Description

Currently lockername.scripts.mit.edu gives a certificate error. We have a valid certificate for *.scripts.mit.edu but it is currently not used. The problem is that (modulo recent extensions) the HTTPS protocol doesn’t support sending the virtual host name before the server must decide which certificate to present.

There have been two proposed solutions. One is to use the SNI extension. This requires upgrading OpenSSL to at least 0.9.8f, patching mod_ssl, and using relatively recent browsers (old browsers will fall back to the current behavior).

The other is to move *.scripts.mit.edu to a separate IP from scripts.mit.edu, so that the server knows which certificate to present based on the IP. This is less general (we can’t extend this to work with arbitrary vhosts), but we could probably implement it now.

#21 fixed upgrade out of Rails vulnerabilities mitchb price
Description

We have 1.2.3 and some older Rails installed, and 1.2.3 is vulnerable. 1.2.5 is fixed. Some users may be using 1.2.3 (we also have 2.something), so we should get them upgraded.

Hopefully this just means installing 1.2.5 and deleting 1.2.3; if these were, eg, Python versions, that'd be true. We don't know enough about Rails to know if it'll be that easy, or require changes to users' scripts.

Was https://help.mit.edu/?q=526978.

---------- Forwarded message ----------
Date: Wed, 14 Nov 2007 22:14:44 +0100
From: Pierre-Yves Rofes <py@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: full-disclosure@lists.grok.org.uk, bugtraq@securityfocus.com,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200711-17 ] Ruby on Rails: Multiple
vulnerabilities

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200711-17
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Severity: Normal
Title: Ruby on Rails: Multiple vulnerabilities
Date: November 14, 2007
Bugs: #195315, #182223
ID: 200711-17

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

Several vulnerabilities were found in Ruby on Rails allowing for file
disclosure and theft of user credentials.

Background
==========

Ruby on Rails is a free web framework used to develop database-driven
web applications.

Affected packages
=================

-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 dev-ruby/rails < 1.2.5 >= 1.2.5

Description
===========

candlerb found that ActiveResource, when processing responses using the
Hash.from_xml() function, does not properly sanitize filenames
(CVE-2007-5380). The session management functionality allowed the
"session_id" to be set in the URL (CVE-2007-5380). BCC discovered that
the to_json() function does not properly sanitize input before
returning it to the user (CVE-2007-3227).

Impact
======

Unauthenticated remote attackers could exploit these vulnerabilities to
determine the existence of files or to read the contents of arbitrary
XML files; conduct session fixation attacks and gain unauthorized
access; and to execute arbitrary HTML and script code in a user's
browser session in context of an affected site by enticing a user to
browse a specially crafted URL.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Ruby on Rails users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-ruby/rails-1.2.5"

References
==========

[ 1 ] CVE-2007-3227
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-3227
[ 2 ] CVE-2007-5379
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5379
[ 3 ] CVE-2007-5380
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5380

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

http://security.gentoo.org/glsa/glsa-200711-17.xml

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.

License
=======

Copyright 2007 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/2.5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHO2VEuhJ+ozIKI5gRAhtQAJ4/nC4Lhyg3HnpGUcyPSr7JIq5BrACfR6vF
jsBmdVGMQCK1OV5oGd1Pnlc=
=aSWR
-----END PGP SIGNATURE-----
-- 
gentoo-announce@gentoo.org mailing list
Note: See TracQuery for help on using queries.