4 ms·
I think you are misreading me. I can, and do, secure Redis instances when I use them. But I am paid to make systems secure and scalable. That's my business, and
by eropple 10y ago
I think you are misreading me. I can, and do, secure Redis instances when I use them. But I am paid to make systems secure and scalable. That's my business, and I have invested extensive time and effort in being able to do so. I don't have a problem when I'm using it. But you accidentally stumble on it here:
> what business do they have setting up servers at all?
That's a very good question, isn't it? I mean, I'd say they don't. But, despite my generally full dance card, most developers who don't have any business doing that at all...do.
Security is ultimately a group effort, that means it falls to those of us who do give a shit to provide what measures we can for those who don't. We have decided that we want developers who are incompetent to pretend to competence. There are pragmatic, practical firebreaks that we must implement to prevent them from hurting other people. You know, from hurting me and you.
- dahart 10y agoAdding https support to Redis would only do what you suggest -- add pretend competence, and hide real problems. It wouldn't add real security. It's better for the sake of ignorant users for Redis to advertise that it's insecure and they're on their own than it is to hide the ignorance. You didn't answer any of my questions. What is your use case? In what situations do you need https support? Why should Redis be thought of differently than memcached or SQLite or ImageMagick or any other program intended for strictly internal use?
- eropple 10y ago> It's better for the sake of ignorant users for Redis to advertise that it's insecure It doesn't advertise any such thing. The manual people don't fucking read isn't advertisement because this is the future, a five-minute-demo is all you need, just grab it and start coding away. In a future populated by competence, I would fully and completely agree with you that Redis does enough. We live in a bad future. Sucks, but--the priesthood of competence has responsibilities. > In what situations do you need https support? "I am talking over a network." It's not a complicated use case. TLS end-to-end, full-stop, is the only tenable future. It's still imperfect, but it's leagues better than unencrypted-over-the-wire, even inside of a theoretically secure ('cause it probably isn't) network perimeter.
- dahart 10y ago> It doesn't advertise any such thing. That statement is false. I realize you feel strongly about this. I realize people sometimes don't read the manual. That doesn't mean the documentation doesn't exist. That doesn't mean Redis didn't try. I'm sorry your view of other developers is so pessimistic, but just because some people do things without enough preparation doesn't mean the entire world needs to cater to their ignorance. You still haven't answered my question: Why should Redis be thought of differently than memcached or SQLite or ImageMagick or any other program intended for strictly internal use? There's a lot of software that uses HTTP connectivity for internal network features. Just because it exists and could be dangerous doesn't mean that HTTPS is the right answer. Redis is designed for performance and not necessarily intended for a network at all. You are the one misunderstanding what Redis is even for, and you are the one failing to RTFM. You are complaining that people are ignorant of how to use Redis, but you are demonstrating your own ignorance here. Redis can't do what it's designed for if it switches to HTTPS-only connectivity.
- eropple 10y ago> That statement is false. I realize you feel strongly about this. I realize people sometimes don't read the manual. That doesn't mean the documentation doesn't exist. That doesn't mean Redis didn't try. It doesn't dump detailed warnings in its log when it starts up and detects that it's being accessed externally in an unencrypted message. It doesn't require REDIS_INSECURE_OK to be set to 1. There's a note in the manual nobody reads. You want to advertise? You make it hard to miss. You demand the acknowledgement of the drawbacks of your gear. You make sure they know, you don't just drop a note and walk away. Yeah, that's harder than "well, not our problem." Such is the responsibility of doing things people need to trust. > I'm sorry your view of other developers is so pessimistic, but just because some people do things without enough preparation doesn't mean the entire world needs to cater to their ignorance. Bullshit and worse words. Yes, many developers are incurious, dim, and ignorant. That doesn't mean we leave them to rot on the side of the road. Security is a group effort. Your attitude is the precise selfish, dirty one that we must fight, because none of us gets out of here without all of us. > You still haven't answered my question: Why should Redis be thought of differently than memcached or SQLite or ImageMagick or any other program intended for strictly internal use? It's not different from memcached. Memcached is fucking up, too. (And, just like Redis, the idea that memcached is intended for "strictly internal" use is perfect hogwash. It is intended for "trusted environments", and no such environment actually exists, to the degree that Redis is perpetuating a bad state of affairs by pretending to it.) ImageMagick? Local software, no network communication, I couldn't care less. OpenCV? Dunno, never used it. > Redis is designed for performance and not necessarily intended for a network at all. You are the one misunderstanding what Redis is even for, and you are the one failing to RTFM. Redis isn't intended for a network? Dang, my ignorance is showing, it's so good of you to fuckin' lecture me; I certainly haven't administered Redis in every documented configuration and my current clients certainly aren't using it for 1m/sec queries. But you're rectally sourcing your claims; if it's not a network service, it shouldn't default to listening on a network port, but rather a socket (like that so-very-different-in-its-aims,-according-to-you Postgres does!), and then everyone's happy! But it does. Because antirez understands that the overwhelming use case for the use of the software is network service. In the event that you are the fraction-of-one-percent who desperately, shirt-rendingly needs that Peak Performance Redis (you don't), you can run it on an unencrypted socket. There's no reason that everyone else shouldn't have TLS-on-a-port by default.