News for hackers. Stuff that matters.
Re:Heroku Fucking Console by mdavidn on Friday March 01, 2013 @11:39AM (#5305242)
This one annoyed me recently.

  $ bundle
  The source :rubygems is deprecated because HTTP requests are insecure.
  Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.
Why can't Bundler just use the new URL? Or, better yet, assume https://rubygems.org unless I specify sources in my Gemfile?
Re:Heroku Fucking Console by steveklabnik on Friday March 01, 2013 @12:22PM (#5305550)
SemVer means you can't break backwards compatibility. Everyone loves not breaking compatibility until they want a breaking change.
Re:Heroku Fucking Console by dragonwriter on Friday March 01, 2013 @01:05PM (#5305846)
> SemVer means you can't break backwards compatibility.

No, SemVer means you increment major version numbers if, and only if, you break backwards compatibility.

Re:Heroku Fucking Console by steveklabnik on Friday March 01, 2013 @01:07PM (#5305865)
Right, and therefore, if you don't want to increment the major version number, you can't break compatibility. I am really not going to get into an argument about this, you're being ridiculous.
Re:Heroku Fucking Console by dragonwriter on Friday March 01, 2013 @01:25PM (#5305967)
> Right, and therefore, if you don't want to increment the major version number, you can't break compatibility.

That's true, but both silly and not what you said before.

There's no good reason to care about version numbers in and of themselves, if you care about them at all, its because of their semantics: using SemVer doesn't make you not want to break backward compatibility, not wanting to break backward compatibility is independent of the use of SemVer. Of course, if you don't want to break backward compatibility, you won't end up bumping the major version number under SemVer, but you've got the whole direction of cause-and-effect wired backward when you say that SemVer is the reason not to break backward compatibility.

Re:Heroku Fucking Console by dasil003 on Friday March 01, 2013 @05:00PM (#5307217)
Okay let me spell it out for you:

No one wants a major version bump in Bundler in order to change the primary rubygems URL because historically there is a lot of potential pain in Bundler updates, and so you better be getting something new that's worth the pain, not just a superficial change that happens to break compatibility only as a technicality.

Re:Heroku Fucking Console by dragonwriter on Friday March 01, 2013 @06:35PM (#5307655)
> No one wants a major version bump in Bundler in order to change the primary rubygems URL because historically there is a lot of potential pain in Bundler updates

SemVer seems pretty much tangential to that, that's a problem with the particular history of the particular project.

If the original claim had been "Bundler's history of major version updates means that they don't want to bump their major version; combined with their commitment to SemVer, that means that any backward incompatible changes are avoided", rather than just that SemVer alone led to people in general seeking to avoid backward-incompatible changes, I wouldn't have challenged it.

Re:Heroku Fucking Console by izietto on Friday March 01, 2013 @01:26PM (#5305973)
So, which is the reason that takes someone to be scared about incrementing the major number?
Re:Heroku Fucking Console by grey-area on Friday March 01, 2013 @02:13PM (#5306297)
End users expect major changes with a major number release (rightly or wrongly), so if you don't have any other than a minor breaking change, they might be annoyed. Of course if you're using semantic versioning you should probably just ignore them and increment anyway till they get used to it.
Re:Heroku Fucking Console by dragonwriter on Friday March 01, 2013 @02:38PM (#5306459)
> End users expect major changes with a major number release (rightly or wrongly)

I think that's highly dependent on the particular market that a product is in, and how its version numbers are used in marketing. Chrome (which neither heavily markets around version numbers nor uses SemVer, but instead increments the major version number with every regularly-scheduled feature release) end-users (whether you are speaking of regular end-users or developers) probably don't have any particular expectations tied to major version bumps.

Microsoft Windows (which doesn't use SemVer, but does heavily market around major versions) end-users probably have much bigger expectations for major versions, as a direct result of the vendor's marketing investments.

A developer-focussed product that consistently uses SemVer and markets around particular new features rather than major version numbers probably won't have much expectation from its target users tied to major release bumps except that they will meet the SemVer definition of a major release bump.

Re:Heroku Fucking Console by Karunamon on Friday March 01, 2013 @02:25PM (#5306378)
This may be a terrifically silly question, but here goes anyways:

What sensitive data are people passing back and forth to rubygems of all places that needs encryption? Especially in the context of a bundle where you're more likely than not pulling down or updating gems (from a public repository, which contains no sensitive data)? And this need is apparently so pressing that it should be complained about to the user?

Re:Heroku Fucking Console by acdha on Friday March 01, 2013 @02:35PM (#5306439)
You're installing code to run using your privileges. Don't you want protection against MITM attacks?
Re:Heroku Fucking Console by sneak on Friday March 01, 2013 @05:06PM (#5307245)
That's why everyone who runs a package repository who isn't a shitdick SIGNS THEIR FUCKING PACKAGES. It protects against tampering on the mirrors, too, with the added bonus that you don't need SSL.

Oh, wait, this is rubyland. Nevermind.

Re:Heroku Fucking Console by Karunamon on Friday March 01, 2013 @02:37PM (#5306452)
And there's the confirmation that it was a silly question.

I've been on a plane all morning and am in no condition to be parsing the topics here :)

Re:Heroku Fucking Console by ville on Friday March 01, 2013 @02:44PM (#5306503)
Confidentiality is not the only feature of HTTPS. Using HTTPS can also protect from simplest man-in-the-middle attacks by validating the certificate, thus improving data integrity.
Re:Heroku Fucking Console by geoka9 on Friday March 01, 2013 @12:01PM (#5305410)
Maybe because it wants you to be in control?

What they probably could do, though, is a 302 redirect to https. But that's frown upon by some, too.

Re:Heroku Fucking Console by tinco on Friday March 01, 2013 @12:20PM (#5305532)
It's not just frowned upon. Having a 302 redirect is almost as insecure as not upgrading to https at all.

In browsers this is sort of acceptable because they let you visually confirm that you've been upgraded to https, and are now securely connected to the right server.

In a text mode app that does the connection behind the scenes and fully automatically, there's no such confirmation or even intervention, so there's no perceptible difference between http and http 302 to https.

Ruby (on Rails) values convention over configuration. It should have made https obligatory per default and overrideable with a flag per this guideline.

Re:Heroku Fucking Console by vidarh on Friday March 01, 2013 @01:42PM (#5306067)
> In a text mode app that does the connection behind the scenes and fully automatically, there's no such confirmation or even intervention, so there's no perceptible difference between http and http 302 to https.

This assumes the client doesn't kick up a fuzz. The entire point is Bundler now does kick up a fuzz. But it could also be made to follow any redirect first, and only kick up a fuzz if the final resource is not https.

Re:Heroku Fucking Console by ptomato on Friday March 01, 2013 @02:04PM (#5306219)
That really doesn't provide any security advantage over just using http. The point of https is to prevent mitm and in this case there's nothing preventing somebody from mitming the original http connection and redirecting to an evil https site.
Re:Heroku Fucking Console by singlow on Friday March 01, 2013 @03:38PM (#5306809)
It could only allow redirect to the same domain and complain if a cert check failed.
Re:Heroku Fucking Console by mdavidn on Friday March 01, 2013 @12:13PM (#5305486)
I only want to be in control when my use case differs from the common case. I would wager that at least 95% of Gemfiles could source https://rubygems.org implicitly and automatically.
Re:Heroku Fucking Console by steveklabnik on Friday March 01, 2013 @12:31PM (#5305621)
You can't guarantee that Ruby has OpenSSL support compiled in, it's not required.
Re:Heroku Fucking Console by vidarh on Friday March 01, 2013 @01:45PM (#5306087)
But you can check, and fail if the user specifies https and it's not present, and give a warning if the user doesn't specify anything or specifies http and OpenSSL is not present.

I still think mdavidn is probably right that 95% or similarly high number has OpenSSL available, and it makes little sense to inconvenience all of those users when you can inconvenience "just" the few who don't instead.