Created attachment 920649 [details]
a simple patch to fix this bug.

Description of problem:
A password containing '?' or other "reserved" character would fail validation.

Version-Release number of selected component (if applicable):
ruby-libs-2.0.0.353-20.el7.x86_64

How reproducible:
every time.

Steps to Reproduce:
1. yum -y update to update the os
2. run the following 
3. run this ruby snippet
----8<-------------8<-----
#! /usr/bin/env ruby

require 'uri/generic'

puts "reserved==#{URI::REGEXP::PATTERN::RESERVED}"

passwords = [ 'password1', 'password?']
passwords.each do |pass|
	puts "== to try with pass=(#{pass})"
	userinfo = "login:#{pass}"
	uri = URI::Generic.new('http', userinfo, 'localhost', 80, nil, '/v1', nil, '', '') 
	uri.userinfo=(userinfo)
end
----8<-------------8<-----

Actual results:
reserved==;/?:@&=+$,\[\]
== to try with pass=(password1)
== to try with pass=(password?)
/usr/share/ruby/uri/generic.rb:440:in `check_password': bad component(expected user component): password? (URI::InvalidComponentError)
	from /usr/share/ruby/uri/generic.rb:390:in `check_userinfo'
	from /usr/share/ruby/uri/generic.rb:455:in `userinfo='
	from /tmp/1:12:in `block in <main>'
	from /tmp/1:8:in `each'
	from /tmp/1:8:in `<main>'

Expected results:
no error thrown

Additional info:
The attached patch is verified as a fix for this particular problem.
btw, not sure this is by design or not: ruby-libs is not a valid component to report this against.
This is rather serious, I'd say, since many sites require non-alphanumerics.
reserved==;/?:@&=+$,\[\]
== to try with pass=(password1)
== to try with pass=(password?)