I recently switched from Ubuntu 10.04 gnome to Debian wheezy Kde. Everything's work fine, except to the Iceweasel/firefox custom protocols! I added komodo.protocol in my ~/.kde/share/services with: [Protocol] exec=python /path/to/my/script.py "%u" protocol=komodo input=none output=none helper=true listing= reading=false writing=false makedir=false deleting=false **This works for chrom(e|ium), but not for firefox.** I've read about firefox should use the gnome configs even under Kde, so I tried: gconftool-2 -s /desktop/gnome/url-handlers/komodo/enabled --type Boolean true gconftool-2 -s /desktop/gnome/url-handlers/komodo/command 'python /path/to/my/script.py %s' --type String that used to work when I was on ubuntu, but it doesn't on kde. Any idea? **EDIT** An example link: komodo:/var/www/app/0/Modules/Controller/Node/Controller_Node.class.php:1202 And if I run the command komodo /var/www/app/0/Modules/Controller/Node/Controller_Node.class.php:1202 from the terminal it works correctly; my python script simply check few things and then runs this command - but with firefox/iceweasel it never gets triggered.

Trying to move a window by grip-able button. On 2 other window managers, and no manager it works fine. Windows move anywhere you want pass display edge bounds. On GNOME Shell and Mutter(Gala) the window is confined to the desktop view with no part of it allowed past display edges. On Compiz I use _NET_WM_MOVERESIZE, other 2 are grab_pointer. The mutter variants won't work using _NET_WM_MOVERESIZE which is fine, but I can't figure out what property to set on the window to allow normal configure messages to get past display limits. Hint as to which it is would be appreciated, kinda would like to support the variant. Need a window_property_set or client message to root to be able to use configure_window. Using code:

#if USE_XLIB
  XMoveWindow(display, motion->event, values, values);
#else
  xcb_configure_window(session->connection, motion->event,
               XCB_CONFIG_WINDOW_X | XCB_CONFIG_WINDOW_Y, values);
#endif

This will only allow movement to the confines of 'maximize' window display. Moving left, negative x values get converted by GNOME to 0. Moving toward bottom, any value greater than window.y + window.height gets converted to display height - taskbar height - window height by GNOME. Verified by values received on configure notify. Do I need to delete a _NET_WM_STRUT property on my window or root window to use? Looking at gdk3 code they use the Xlib variant of code. **Solved**\ Problem is issue that GNOME only supports move of window correctly through their toolkit. It appears to lack proper support of both EWMH and ICCCM. Workaround is to use override-redirect, taking away its ability to mess with configure message.

I'm interested in a single command that would download the contents of a torrent (and perhaps participate as a seed following the download, until I stop it). Usually, there is a torrent-client daemon which should be started separately beforehand, and a client to control (like transmission-remote). But I'm looking for the simplicity of wget or curl: give one command, get the result after a while.

I'm trying to issue a bash command on infrared remote control button presses. The IR receiver device is an usb device included in the Anysee e30 Combo plus DVB-T tuner, which works perfectly, otherwise. The output of the ir-keytable output: Found /sys/class/rc/rc0/ (/dev/input/event0) with: Driver dvb_usb_anysee, table rc-anysee Supported protocols: NEC Enabled protocols: Name: Anysee bus: 3, vendor/product: 1c73:861f, version: 0x0100 Repeat delay = 500 ms, repeat period = 125 ms When I run ir-keytable -t to test whether the button presses are received, this works and I see scan codes and button labels(KEY_UP etc) showing up. To make a button press fire a bash conmmand, I think my only option is to use LIRC's irexec command. In installed lirc and configured it, then ran irw which is lirc's testing command. No output whatsoever. I checked that lircd is running and that irw can connect to the daemon. Note that LIRC is not under supported protocols of the ir-keytable command. Does this mean I can't use the hardware for this purpose? root@raspberrypi:/home/pi# modprobe ir-lirc-codec root@raspberrypi:/home/pi# ir-keytable -c -p NEC,LIRC Old keytable cleared /sys/class/rc/rc0//protocols: Invalid argument Couldn't change the IR protocols I saw on a few websites that people do this to add lirc as a protocol. I am not surprised this failed for me though, it would be odd that you could add an unsupported protocol by simply echoing it's name to a file. root@raspberrypi:/home/pi# echo lirc > /sys/class/rc/rc0/protocols bash: echo: write error: Invalid argument I am using a Raspberry Pi v2 as system (Debian Wheezy)

As we work with a local drive, we create read and write requests to the backend block devices. In general, they can not be and should not be fulfilled in their issue order. For example, write requests can happen with a delay (typically, in free time as the write cache is too big), and also read requests can be served much more quickly from the page cache. Thing are becoming much more problematic if we work with a network shared block device. The 3 ways I know: * nbd, alias network block device * iscsi, that is scsi protocol over a tcp socket * and we can also use ordinary files mounted on an nfs or cifs directory. However, things are not so simple over a network connection. That happens typically over tcp, and tcp serializes the communication, do we want or not. Thus, concurrent requests over a tcp-shared network block device, must be fulfilled as they arrived over the network. That is not always the correct way to do, not even in the case of today with broadly used SSD backends, simply because cached memory pages could be served on the spot. In my opinion, the obvious solution would be to use some more advanced protocol to handle correctness and giving more freedom over the ordering of the requests. That could be maybe sctp or dccp. They are well developed protocols in the linux kernel, and they make possible to reorder the answers, compared to their issue timestamp or network arrival order. Does such a thing exist? As far I can see, * nbd is tcp-only * nfs can be also udp, but that is sub-optimal * iscsi is also tcp-only. Does some way exist to use some more advanced protocol for the network sharing of a block device?

I want to accomplish something unique and use HTTP instead of HTTPS for using all kinds of different websites, and was wondering if anyone has any ideas about how to accomplish this feat. The internet is very difficult to search these days, and gives results like...search with https! And basically ignores my requests. I think it's interesting, and am always looking for unique ways to use technology which afford us different benefits. I think http is interesting because I have seen a lot of different websites making strange unsolicited connections, and generally being up to lots of sneaky behavior, so with http we can hopefully examine these types of connections in more detail, and better understand sneaky behavior that evolves over time. Anywho I am going to continue researching this line of thinking, and if anyone out there in the void has an idea to input that may be helpful that would... be helpful. thank you edit: so I'm digging around and found some basic answers that are unhelpful to me, such as using firefox settings to disable https redirection. browser.fixup.fallback-to-https false (doesn't alter the situation) https://stackoverflow.com/questions/30532471/firefox-redirects-to-https I think that either our dns servers, or perhaps web servers themselves will attempt to force us all to use https, so perhaps the only true solution is going to be to deny the https protocol itself entirely on the local host, and if remote web servers refuse to connect via http than we can safely disregard them as insecure, and find alternatives. It's also likely that in order for this strategy to succeed we will need unique solutions instead, of just one solution, because technology will adapt new methods to inappropriately impose constraints on our, in this case, interactions with remote web servers. So I'm pressing ahead with this issue and trying different things, here's how I disabled https on the local host using gufw (added a simple rule to deny incoming/outgoing https) [img] [/img] It's concerning because I've noticed that unsolicited connections will come to, and from, my browser, and there's no way to know what initiated these exchanges, or what they are doing. Disabling https completely with my firewall on my own computer prevents firefox from accessing lots of websites.. like this one: unix.stackexchange.com and google. (they attempt to load in an infinite loop) However using a different web browser, lynx, I can connect to google with http immediately. [img] [/img]

Is the tc tool only useful for TPC traffic, or can it also be used to control other protocols like UDP traffic?

When configuring ssl.conf for Apache 2.2.4, I want to use some configuration like the below: SSLEngine on SSLCertificateFile /opt/alfresco/deploy/ssl/crt/testdns.com.crt SSLCertificateKeyFile /opt/alfresco/deploy/ssl/private/testdns.com.key SSLCertificateChainFile /opt/alfresco/deploy/ssl/crt/intermediate.crt SSLVerifyClient none SSLVerifyDepth 1 SSLOptions +StdEnvVars +StrictRequire SSLProtocol -ALL +TLSv1 SetEnv nokeepalive ssl-unclean-shutdown SSLProtocol +TLSv1 +TLSV1.2 When I use +TLSv1 only, it gives me some error like below for my API calls: javax.net.ssl.SSLException: Received fatal alert: protocol_version If I use both protocols SSLProtocol +TLSv1 +TLSv2, it gives a browser “Not secure” indicator.  How do I prevent it? Cases are as follows: - If I use only +TLSv1: My API calls are working fine. - If I use only +TLSv2: Browser shows secure icon, but API call fails and gives the above error. - If I use both, still browser shows “Not secure” icon. What is the solution for it?

I'm using telnet to connect to a serial port via a TCP/IP server. I need a raw, unfiltered, unbuffered connection, and can get most of the way there, but no matter what I do telnet sends protocol negotiation commands when it connects. This is strange, because "man telnet" page says: When connecting to ports other than the telnet port, telnet does not attempt telnet protocol negotiations. This makes it possible to connect to services that do not support the telnet protocol without making a mess. But, although I'm connecting to a non-standard port, telnet negotiates: linuxdev:~ griscom$ telnet 172.16.250.49 2023 Trying 172.16.250.49... Negotiating binary mode with remote host. Connected to 172.16.250.49. Escape character is '^]'. And, as the man page warns, this makes a mess. Is there a way to use telnet as a completely transparent TCP/IP client? Or, is there some other tool I could use? Details: * Running telnet on an Ubuntu 22.04 system * Server is a [USR-TCP232-T2 ethernet to serial converter](https://www.pusr.com/products/serial-to-ethernet-converter-modules-usr-tcp232-t2.html) * Serial port is connected to a Linux system's console, so I need unbuffered transparency so I can, e.g. run vim or type control characters Edit: I figured out the problem. telnet by default runs in "line" mode, collecting characters and sending them the next time a CR is typed. I need it to run in "character" mode, where it sends data as-is. Problem: I can't set "character" mode without telnet negotiating that change with the other end of the line. Proof: if I connect to the serial adapter with an unconfigured telnet, I'll get no negotiation characters sent to the adaptor. But, if I use ^] to drop into command mode, and then type mode character, telnet will immediately negotiate with the other end, making a mess. (The same thing happens if I use a .telnetrc file to configure the connection to character mode.) So, there's no way for telnet to connect to a port in "character" model without sending spurious command bytes to that port. I'll need a different solution.

I am running Samba 3.6 in SLES 11.4. I recently added in /etc/samba/smb.conf in the [global] section the following - min protocol = SMB2 - max protocol = SMB2 this was done to allow communication with Windows 10 clients that are starting to come online, and also continue to work with existing win7 PCs. **Does anyone know or how can i find out, the available protocols I can use?** I thought, and tried, setting the min & max protocol to SMB2.1 but my test client which is Windows7 immediately fails to connect. I thought SMB2.1 was available in win7? And how do I know SMB2.1 is a valid choice in Samba 3.6? Is SMB3 a valid choice in Samba v3.6?

Suppose,I am using DNS over Quic. Since it is an encrypted protocol as it claims. My question is if intermediate servers cannot see my dns query, how will my dns query be resolved? It says that the query is encrypted between client and the server. So how will my resolver know which authoritative server to forward this query to?

I want to know if I can somehow disable congestion control in QUIC.

in RHEL 8.8 when I am trying to test NFS tcp versus udp and versions 3 versus 4.0, 4.1 and 4.2, I observe on my nfs client a mountproto= in addition to proto= when typing mount. What is the significance of this and what does it mean? Should I be able to, in RHEL 8.8, have NFS operating showing specifically vers=3 and proto=udp on the nfs client? What does it mean, on the nfs client, when I see proto=tcp and mountproto=udp ?

The module vfs_full_audit in Samba lists objects that can be added to the module to increase the logging specificity or verbosity generally of syscalls. Example: # defaults for auditing full_audit:priority = notice full_audit:facility = local6 full_audit:failure = create_file open opendir rmdir unlink unlinkat connect connectpath disconnect full_audit:success = rename opendir rmdir unlink open create_file opendir unlinkat connect connectpath disconnect full_audit:prefix = %U|%d|%u|%R|%I|%S However in the man page located here: https://www.samba.org/samba/docs/current/man-html/vfs_full_audit.8.html It fails to define explicitly what each object actually does - I understand that some of them are fairly obvious such as "open" or "rmdir" but a sentence just describing what each part does would be very useful for more questionable ones such as "kernel_flock" Does anyone know of any resource/URL that defines these values explicitly? Or perhaps this has been asked previously by one of you and had data back from Sernet detailing it? Thanks for looking ;)

This question applies not only to the FTP protocol, but also to other protocols in general. We call FTP a protocol, but speaking literally, FTP has a source code. When an ftpd service is running on a server, how does this service access and make use of the FTP source code? Is the source code embedded into the ftpd service? Many thanks and cheers.

This is nothing new to me at least, that SATA actually "talks" SCSI, hence why these SATA devices show up as SCSI devices in Linux. A related question has been asked before, e.g. https://unix.stackexchange.com/questions/3901/why-do-my-sata-devices-show-up-under-proc-scsi-scsi However what fails to be mentioned where I've seen this discussed before is exactly in what sense SATA relates to SCSI, and how they differ. I assume it is taken for granted that they differ on the physical layer, as they do not share compatible cables. However what about higher up on the stack? I am aware of how Linux represents SATA and even IDE disks on modern kernels as just SCSI to the SCSI subsystem. But what about the actual protocol that is used on the bus? I also know that ATAPI is an encapsulation for SCSI, but what about regular ATA? I've noticed that features from SCSI such as NCQ, FUA, DPO, etc (if I don't remember incorrectly) have been adopted from SCSI. But it is unclear how "much" of the SCSI command set is actually shared or similar. Do modern SATA devices with their ATA specification implement a subset of the SCSI command set, but encapsulated (as in ATAPI)? An identical set? A superset? Or perhaps only selected features are implemented as variants that are not directly identical? Where can I find some clear information on this, and especially how it relates to the Linux kernel? Some kind of tutorial for driver development would be nice, but even just an overview that doesn't completely skip over all the details would suffice. I am aware I can just read the actual specification, but that is again much too detailed, hard to find what you're really looking for, and just not realistic for me and probably most other users in the temporal sense.

Given that I have the infohash of a torrent and the URL of a BitTorrent tracker (e.g. udp://tracker.example.com/announce), how do I use the command line to get all the IP addresses of peers that the tracker knows about? I am using Ubuntu 20.04.

I have a proprietary Linux system, with a proprietary init system, which uses a serial console. I lately noticed, that the xon/xoff flow control is active on this serial console, which poses the risk of hanging the boot process when the xon character (0x13) is received by line noise. Looking at other systems with serial consoles (systemd based) shows that flow control is disabled there for the serial console, which seems sane. The question is, which part of the system is responsible for deactivating the flow control of the console tty? Is this done by the init process or the kernel itself? I.e., is this an error within the kernel configuration or must the init system be fixed to disable the flow control? I know, that the flow control can be disabled using the

()

function or by running

-ixon -F /dev/console

, but for a reliable system, this should be disabled before any process writes output to the console. I already browsed the systemd source code but wasn't able to find any code disabling flow control there.

I'm using *Putty* or *Picocom* to talk directly to a Mobile Modem using AT commands, while doing some experiments that require up/downloading some files on the mobile module's EFS partition. The protocol used to do this is *Xmodem* and it seem that most terminal utilities no longer include/support this. Picocom does as a 3rd party dependence: Picocom can send and receive files over the serial port using external programs that implement the respective protocols. In Linux typical programs for this purpose are: • rx(1) - receive using the X-MODEM protocol * • rb(1) - receive using the Y-MODEM protocol • rz(1) - receive using the Z-MODEM protocol • sx(1) - send using the X-MODEM protocol * • sb(1) - send using the Y-MODEM protocol • sz(1) - send using the Z-MODEM protocol However, none of these are available for Win/Cygwin and I'm not able to find the sources to compile these. (Where are these hosted these days?) **Q: What would be the easiest way to receive Xmodem data using command line?** (What other simple alternatives are there?) I have already looked at the following Unix SE questions: * https://unix.stackexchange.com/questions/111749/how-to-send-a-file-using-xmodem-protocol-from-the-command-line * https://unix.stackexchange.com/questions/239370/send-a-file-over-xmodem-with-payload-size-64 * https://unix.stackexchange.com/questions/56614/send-file-by-xmodem-or-kermit-protocol-with-gnu-screen

I have a postgres 9.1 server running on the default port 5432 on an Ubuntu 12.04 cloud server. I want to open up the port, so I can make remote queries -- but I have to open the port on IP tables, which requires that I specify a protocol. This doc does not mention TCP/UDP, etc. What protocol should I permit in IP tables?