Re: [DNG] [ASCII] [Mutt+Torify+Fetchmail+Procmail+Msmtp] Problems torifying email
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/05/2019 06.31, Se7en wrote: > The problem I have been having since November 2018 when I upgraded > to ASCII was that I simply can not torify Fetchmail. I later > discovered that Mutt is affected. The problem seems to be related > to my mail spool, /var/mail/se7en. Are you using torsocks to torify applications? I wouldn't recommend that. Using iptables, it's possible to configure tor as a transparent proxy. You can redirect network traffic using iptables over tor. That can be just traffic from the local host, or even traffic from a whole network. Using linux network namespaces, you can have different independent internal network configurations on your machine. You can then enter that namespace and execute an application there. To route traffic between network namespaces, you can use virtual ethernet interface pairs (veth). It is also possible to connect them using bridges. Physical network interfaces can be moved to a different network namespace as well. All this can be done using the "ip", "brctl" and "iptables" commands. You can also use containers for this, they usually use network namespacces too. I recommend torifying the complete system if possible, or even better, a whole dedicated network. If you keep the tor devices and the other devices completely seperate, it becomes much harder to deanonymize you. Use one thing in both environments, and you may have been deanonymized. On another note, there are also a lot of online services that block tor nodes, and i think some ports like smtp are blocked on pretty much all exit nodes. It's fine for mailing between onion addresses, but not for sending mails anywhere else from within tor. Good luck, Daniel Abrecht -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEZT8xKpcJ1eXNKSM1cASjafdLVoEFAlzcil0ACgkQcASjafdL VoFkCQgArT1EdxEj8NxuoxJNJu3m4gwKlxoRVseYZByKVdiJwUar0L6/RLm3Ug3E 8k2hunHzK27xqFl6epeRKryzZl1X3kQsM31y8aclQlgdzHP6Mv8HXaY9wlIHaF6a kSj9R+YxZb0OLY0i2RH8rybfze0lH0CwMx8yhZkgV087lI+1UW4H1NYantN/2p8I KOWPo5MoHxmqPkNgMBVHaCD20QWPuwhCNrxjgln9FbRQxyCcDHzV0VTKPxc6YtfP Lo789jEFyB81gW4hQgdWRpzzxoQXQ78PWau3d16z3cDUhUS2lLnsxuHUdPolBPJv Rz8hxXFzm9MOVgUOLLgFzbeDAYJuig== =Hbdy -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] [ASCII] [Mutt+Torify+Fetchmail+Procmail+Msmtp] Problems torifying email
I have previously stated this months ago in the IRC, and have found some references in other bug report forums including Debian, Ubuntu, and FreeBSD, but I have been unable to find a solution for my own problem. The proposed solutions include "Don't use Tor", "Use Dante", and the classic "Nevermind, I figured it out!" The problem I have been having since November 2018 when I upgraded to ASCII was that I simply can not torify Fetchmail. I later discovered that Mutt is affected. The problem seems to be related to my mail spool, /var/mail/se7en. Fetchmail properly downloads the files when torified. The problem is when it attempts to write them to /var/mail/se7en. The output of a torify'd `fetchmail -v` is fetchmail: MDA error while fetching from se7en@cock.em...@mail.cock.li fetchmail: 6.3.26 querying mail.cock.li (protocol IMAP) at Tue 14 May 2019 11:21:55 PM PDT: poll completed fetchmail: Query status=6 (IOERR) fetchmail: normal termination, status 6 Btw, these are the permissions of my /var/mail/ -rw-rw 1 se7en mail 2.8M May 14 23:09 se7en When I attempt to torify mutt (which was part of my previous setup) it produces an error saying "/usr/bin/mutt_dotlock: Operation Not Permitted". (Part of the error is cut off). I can then view my spool's mail, but I can not change the flags or compose a new message. None of these problems occur in a non-tor environment. Is the problem relating to you, Debian Packaging, Tor, Mutt, Fetchmail, or what? Torifying MSMTP works. Torifying almost all-else works. It is only seemingly related to my Procmail+Fetchmail setup. Does /anyone/ have a solution? It has been too long to have such a seemingly-simple problem I can not find a solution to rectify! -- |-/ | Se7en / The One and Only! | se7en@cock.email / | 0x73518A15BA3C1476 / | Website TBA signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] simple-netaid from scratch
Hi Aitor, I, like many other Devuan users, hope that the last crises is over and that it will never happen again. The purpose of replying to your thread is to ask why you are rewriting the backend from the very beginning. Needless to state, I am still using my version of simple-netaid with its simple graphical interface. However, this does not mean I will not consider better competitors. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] simple-netaid from scratch
Hi all, I recently started started developing the backend of simple-netaid from scratch. There will be a lot of improvements. You can find the project here: https://git.devuan.org/aitor_czr/simple-netaid/tree/master/ The readme file will contain all the documentation about usage of the CLI version of simple-netaid. The code contained in the current status are core versions of some features of iproute2, removing simple-netaid's dependency on the whole project. For example, the functions of the ipaddr.c file: https://git.devuan.org/aitor_czr/simple-netaid/blob/master/backend_src/ipaddr.c flushes all the previous ip addresses asigned to a concrete network interface,doing the same than: # ip addr flush dev I hope to finish this work as soon as possible in order to include the network manager in gnuinos ascii. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
