Forum Debian Users Gang

[quote=tajwan]Przydała by się jakaś standaryzacja czy cuś.[/quote]
To właśnie oferuje Windows [ na nieszczęście ].

[quote=Jacekalex]Wiesz w ogóle, po co Tobie są potrzebne dwa jaja, skoro wystarczyłoby jedno?
Jak nie wiesz, to zawsze możesz się pozbyć "zbędnego balastu". :D[/quote]
Trafne porównanie :D

Mac'a se kup...

Czasami myślę, że tego typu tematy są stawiane po to, aby autor się pośmiał jak my na to się 'rzucimy', i będziemy bronić swego... Tylko po co? Jakiś fetysz?

A ja zacytuję jednego developera odnośnie tworzenia gui aplikacji na linuxy:

A Linux GUI is very unlikely to ever see the light.

The protocol will not change in the near future and the proxy will soon be labeled 1.0. This is not the problem.
The problem is writing a GUI for Unix-based systems.

For starters, what would such a GUI look like?

An icon in the menu bar? Mmm... wait, that would only work with some environment, others need an app that fits in the dock. Oh, no, for KDE users, maybe a plasma widget would be the way to go. Ah, but what about people running another environment like XFCE? Ok, XFCE-specific app, then. And what about people just running a window manager? Hey, well, some are scriptable and can be used to add the dnscrypt status to the menubar, or dock, or custom menu. Of course, each of these scriptable window managers use a different script language and API. What about others? Well, this probably should be a standalone app, then. Just for displaying a green light and a drop-down menu? That would be gross. And ugly. And not well-integrated.

Ok, suppose this problem is solved. Now, what would that thing do?

Supposedly, it would 1) start dnscrypt-proxy and 2) change the DNS settings to use it. Oh, and 3) keep track of network changes, like SSID changes, in order to know what the previous resolver was, how to revert to it and how and when a probe for captive portals has to be sent.

Let's start with 1). How to start/stop a service? Furthermore one that requires root privileges? Well, each operating system and each Linux distribution has its own custom system. Oh, and that changes from one version to another. Oh, and of course, users can use their own systems, too. How to start it as a non-root user? How to know if a user is privileged enough to do it? That, also, is very distribution / OS-specific. I can chose to install sudo, or not. To have setuid-disabled mount points, or not.

2) Change the DNS settings. How to do that? Monkey patching /etc/resolv.conf just doesn't work. Operating systems like Solaris have a cache that needs to be invalidated first. Others just don't use this file at all. Linux distros usually automatically update it through distro-specific custom scripts.
But wait! A local caching resolver can also be running (which is not a bad idea at all). Either because the distro installs one by default (like the current Ubuntu snapshots) or because the user installed Unbound/PowerDNS/Bind/PDNS/dnsmasq/whatever.
Ok, so bypassing that in order to directly reach the dnscrypt proxy would be a terrible idea.
So checking the "use dnscrypt" box should also find what resolver software is running, patch its configuration file (that may reside anywhere depending on the OS/distro), restart it (still, no standard way to do that), and that should work with all known resolvers. Oh, and that should work on dead-old versions of these, too, for people running distros with long-term support. And how to revert the settings? Keep a copy of the previous configuration file? What if the user edits it by hand afterwards? Use git? Try and fail at automatically resolving conflicts?
There's just no simple, portable and reliable way to do that.

3) Once again, scripts, devices and configuration files for network-related stuff vary from OS to OS, and from distro to distro. Not to mention that people can add their custom commands to /etc/rc.local and friends in order to accomodate custom setups.

So, a GUI to automatically do 1) 2) and 3) is bound to break things. Or it would work only on some unmodified version of a specific distribution or OS.

dnssec-trigger only ships with Fedora for a reason. And it only works on a vanilla distro, with no local resolvers and no manual configuration ever done to the network configuration. And even to achieve supporting this very specific environment, the author had to work closely with the Fedora project.

OSX and Windows suck in many ways. Yeah, you can't change the window manager. Yeah, the registry / system configuration suck. Yeah, it's mostly closed-source. Yeah, most users don't tweak much, they don't even run any local DNS cache besides the crappy built-in one. But on the other hand, it makes it much much much easier to write a dnscrypt GUI that works in most cases. But even then, our Windows and OSX GUIs have a lot of issues. Dealing with crappy antivirus software, buggy firewalls, captive portals, ISPs redirecting HTTP and DNS traffic, is hard. And that barely works at the moment. Add the challenges that supporting 1), 2) and 3) for a Unix GUI requires, and you get something that has little change to work, and a lot of change to keep our support team very busy. What would be the point of a GUI again? Ah yeah, avoid typing a single command: "dnscrypt-proxy --daemonize" and changing the DNS settings. Well, considering the fact that most Unix users are familiar with the command line, going through the pain of writing a GUI that is likely to break things and cause a lot of troubles is not worth it.[/quote]
Dlatego linux ssie, trza się uczyć obsługi konsoli, a gdy się już to opanuje, gui przestaje być potrzebne i linux przestaje ssac, choć mnie to wkurza jak leżę sobie wieczorem w łóżku z moim... laptopem i chcę go pomiziać, a niektóre appsy nie mają gui i muszę wstawać i palić światło by widzieć co piszę w terminalu, do dupy z taką robotą. xD