Re: Signal [Was:] Re: Encrypt files on Linux, decrypt on Windows
On Ma, 25 aug 20, 14:17:26, Celejar wrote: > > I do use Signal on mobile, and I want to like it, but there are a few > things about it that just really bother me (these may not be relevant > to the OPs situation): I never claimed it's perfect, just that it's not a "black box". See also this comment in one of the discussions you linked that appears to be more balanced: https://github.com/privacytools/privacytools.io/issues/779#issuecomment-471687384 As far as I can tell Signal is still miles ahead of WhatsApp, Telegram, Snapchat, etc. and it's still challenging to get others to use it[1]. One might find that with the "perfect" communication tool there is no one to communicate with :) [1] I basically had to "blackmail" my close family and friends by refusing to install WhatsApp on my private phone. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: How to make dhclient reread its config? (Debian 10)
On Wed, Aug 26, 2020 at 5:56 AM Victor Sudakov wrote: > Dear Colleagues, > > I've made some changes to /etc/dhcp/dhclient.conf, now I need to make > dhclient reread it (and apply the changes to /etc/resolv.conf). > > There seems to be no dhclient service in systemd, and I don't find > any info about signalling dhclient with "kill -HUP" etc. > > "dhclient -x" or "dhclient -r" bring the network down (I've actually > confirmed that on a test host), and I loathe to risk it on a remote box. > A reboot seems too radical. > > Any ideas please? > A simple "dhclient" as root (or "sudo dhclient") without parameters should be enough. In syslog you should be able to see something like this afterwards: Aug 26 06:10:41 mailtest dhclient[899]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Aug 26 06:10:41 mailtest dhclient[899]: DHCPOFFER of 192.168.15.23 from 192.168.15.1 Aug 26 06:10:41 mailtest dhclient[899]: DHCPREQUEST for 192.168.15.23 on eth0 to 255.255.255.255 port 67 Aug 26 06:10:41 mailtest dhclient[899]: DHCPACK of 192.168.15.23 from 192.168.15.1 Aug 26 06:10:41 mailtest dhclient[899]: bound to 192.168.15.23 -- renewal in 73845 seconds.
How to make dhclient reread its config? (Debian 10)
Dear Colleagues, I've made some changes to /etc/dhcp/dhclient.conf, now I need to make dhclient reread it (and apply the changes to /etc/resolv.conf). There seems to be no dhclient service in systemd, and I don't find any info about signalling dhclient with "kill -HUP" etc. "dhclient -x" or "dhclient -r" bring the network down (I've actually confirmed that on a test host), and I loathe to risk it on a remote box. A reboot seems too radical. Any ideas please? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
Re: Get an error when i use new kernel
I'm sorry, I haven't finished. I sent it by mistake， the error log is： [ 26.367633] nvme :01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 26.367633] nvme :01:00.0: AER: device [1e0f:0009] error status/mask=1000/6000 [ 26.367633] nvme :01: AER: [12]Timeout i use lspci to search this device(1e0f:0009),and i got the error device is ➜ ~ lspci -nn |grep 0009 01:00.0 Non-Volatile memory controller [0108]: KIOXIA Corporation Device [1e0f:0009] (rev 01) the device is my ssd I searched the Internet for this error and found some similar errors and solutions, such as in the grub.cfg Riga PCI = ***, etc., but it doesn't work here. I found that their error reporting devices are different from mine stan clay 于2020年8月26日周三 上午10:26写道： > Yesterday, I upgraded unstable from stable and installed a new kernel, but > I couldn't get into the system with the new kernel. I got an error > > > [ 26.367633] nvme :01:00.0: AER: PCIe Bus Error: > severity=Corrected, type=Data Link Layer, (Transmitter ID) > [ 26.367633] nvme :01:00.0: AER: device [1e0f:0009] error > status/mask=1000/6000 > >
Get an error when i use new kernel
Yesterday, I upgraded unstable from stable and installed a new kernel, but I couldn't get into the system with the new kernel. I got an error [ 26.367633] nvme :01:00.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 26.367633] nvme :01:00.0: AER: device [1e0f:0009] error status/mask=1000/6000
Re: Cannot see a process listening on 127.0.0.1
Anssi Saari wrote: > Victor Sudakov writes: > > > It's different in *BSD which got me confused. In *BSD, even if you bind > > to INADDR_ANY, you'll see something like this in sockstat output: > > > > root dovecot39601 21 tcp4 *:110 *:* > > root dovecot39601 22 tcp6 *:110 *:* > > root dovecot39601 23 tcp4 *:995 *:* > > root dovecot39601 24 tcp6 *:995 *:* > > Well, what about using ss instead of netstat on Linux? I don't seem to > have any daemon running that would show different with netstat or ss so > can't check. Basically the same: root@test4:~# netstat -lpn | grep 8081 tcp6 0 0 :::8081 :::*LISTEN 10872/node /home/ad root@test4:~# ss -ln | grep 8081 tcpLISTEN 0 128 :::8081 :::* root@test4:~# -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/ signature.asc Description: PGP signature
Signal [Was:] Re: Encrypt files on Linux, decrypt on Windows
On Sun, 23 Aug 2020 14:03:21 +0300 Andrei POPESCU wrote: > On Vi, 21 aug 20, 13:07:56, Charles Curley wrote: > > On Fri, 21 Aug 2020 13:31:00 -0500 > > Paul Johnson wrote: > > > > > GnuPG. It's in Debian, there's Windows versions on its website, and > > > it's not some mystery box like Signal. > > > > ++ > > > > It also has the advantage that the cryptext will stay encrypted on any > > intermediate servers. WhatsApp and Signal claim their traffic is, but > > one must take their word for it. > > Signal is free and open source software. > > Please do feel free to inspect the source code for potential back doors > or vulnerabilities. I do use Signal on mobile, and I want to like it, but there are a few things about it that just really bother me (these may not be relevant to the OPs situation): 1) The requirement of associating accounts with (real, working) phone numbers. 2) The (current) refusal [1] to provide an option to export messages into a format easily accessible by the user. (I know, I can read and try to understand Signal's code, and then write my own decryptor - thanks, Signal). 3) The strong encouragement of the use of Google's Play Store to install the mobile app, and the strong discouragement of other, FLOSS compatible, methods of installation. [2] Discussion of these and many other issues with Signal: [3] I'm just a user, and not a very advanced one at that, but I can't get away from the feeling that Signal is somewhat user-hostile, with an attitude of "Trust us - Moxie is a legend, our code is great (and FLOSS), and we really care." All true, to be sure, but still. [1] https://github.com/signalapp/Signal-Android/issues/7586 [2] https://signal.org/android/apk/ [3] https://github.com/privacytools/privacytools.io/issues/779 Celejar
Re: Homebuilt NAS: System Drive Filesystem?
On Tue, 25 Aug 2020 09:37:20 +0300 Andrei POPESCU wrote: > On Lu, 24 aug 20, 09:26:57, Patrick Bartek wrote: > > > > Since F2FS is not supported directly for an install, one would have to > > convert to it after or configure the flash drive with another computer > > before the install. I don't know if it is worth the time to do so. > > EXT4 without journaling would be easier. > > The journal is written to only if the filesystem is written to as well. Yes, and every time a log is written to, too. On my main system, normal usage, journaling on, I'm getting hard drive activity about 2 to 3 times a minute 24/7/365. And currently, I have firewall logging off which was writing to log every 2 seconds or so. The two Roku devices I have, for some reason, were trying to access this computer, but no others. Don't know why. Some have suggested to remount / read-only, but since my plan is not to have a separate /home partition, that would cause problems. Probably will cause problems even if I do. However, the NAS software I plan to use (OpenMediaVault) has a specific plugin if you're using solid state devices for the system and/or DATA drives. Don't know exactly what it does, or whether it's a binary or an executable script. Guess I'll have to wait until I get to the point of installing it to see what it does. No details are given in OMV's docs. > Without having any other data than my own, admittedly limited, > experience[1] it doesn't seem worth disabling the journal, it is only > written when the filesystem is written to as well anyway. At least the flash drive I'm using has wear leveling. And I'm going to leave about 15% of it unpartitioned to be safe. Plus, clone it, so if it goes down, I just plug in the clone and I'm up and running. > [1] all my current systems are running from SD cards, with the only > optimisation being to not configure any swap. Thanks for your input. B
Re: Cannot see a process listening on 127.0.0.1
Victor Sudakov writes: > It's different in *BSD which got me confused. In *BSD, even if you bind > to INADDR_ANY, you'll see something like this in sockstat output: > > root dovecot39601 21 tcp4 *:110 *:* > root dovecot39601 22 tcp6 *:110 *:* > root dovecot39601 23 tcp4 *:995 *:* > root dovecot39601 24 tcp6 *:995 *:* Well, what about using ss instead of netstat on Linux? I don't seem to have any daemon running that would show different with netstat or ss so can't check.
