discussion of anonymous remailers.
Bitmessage is the next generation of secure, private communication.
In article <v29l0b$37h5m$1@paganini.bofh.team> anon wrote:
Bitmessage is the next generation of secure, private communication.
Nevertheless you're NOT using Bitmessage to post this message.
So what's wrong with it?
Nomen Nescio wrote:
In article <v29l0b$37h5m$1@paganini.bofh.team> anon wrote:
Bitmessage is the next generation of secure, private communication.
Nevertheless you're NOT using Bitmessage to post this message.
So what's wrong with it?
It is up to remops to allow this.
https://github.com/stefanclaas/mailchuck2mix
Stefan Claas wrote:
Nomen Nescio wrote:
In article <v29l0b$37h5m$1@paganini.bofh.team> anon wrote:
Bitmessage is the next generation of secure, private communication.
Nevertheless you're NOT using Bitmessage to post this message.
So what's wrong with it?
It is up to remops to allow this.
https://github.com/stefanclaas/mailchuck2mix
The other way around is also possible:
https://github.com/stefanclaas/mail2chan
Stefan Claas <pollux@tilde.club> wrote:
Stefan Claas wrote:
Nomen Nescio wrote:
In article <v29l0b$37h5m$1@paganini.bofh.team> anon wrote:
Bitmessage is the next generation of secure, private communication.
Nevertheless you're NOT using Bitmessage to post this message.
So what's wrong with it?
It is up to remops to allow this.
https://github.com/stefanclaas/mailchuck2mix
The other way around is also possible:
https://github.com/stefanclaas/mail2chan
And the gateway gets hold of your plain text message? Just wondering.
Nomen Nescio wrote:
In article <v29l0b$37h5m$1@paganini.bofh.team> anon wrote:
Bitmessage is the next generation of secure, private communication.
Nevertheless you're NOT using Bitmessage to post this message.
So what's wrong with it?
It is up to remops to allow this.
On Sat, 18 May 2024 12:55:13 +0200
Stefan Claas <pollux@tilde.club> wrote:
Nomen Nescio wrote:
In article <v29l0b$37h5m$1@paganini.bofh.team> anon wrote:
Bitmessage is the next generation of secure, private communication.
Nevertheless you're NOT using Bitmessage to post this message.
So what's wrong with it?
It is up to remops to allow this.
Cut out the remop middle man. Escape the mixmaster plantation. Find your true anonymous freedom with Bitmessage.
Privacy - it's what's for dinner. Use Bitmessage so you don't become a meal.
If the Bitmessage client, maybe a CLI Version, would allow us to create
BM payload offline and then inject it later via an online computer, well
that would be very very nice!!!
anon wrote:
On Sat, 18 May 2024 12:55:13 +0200
Stefan Claas <pollux@tilde.club> wrote:
Nomen Nescio wrote:
In article <v29l0b$37h5m$1@paganini.bofh.team> anon wrote:
Bitmessage is the next generation of secure, private communication.
Nevertheless you're NOT using Bitmessage to post this message.
So what's wrong with it?
It is up to remops to allow this.
Cut out the remop middle man. Escape the mixmaster plantation. Find your true anonymous freedom with Bitmessage.
Privacy - it's what's for dinner. Use Bitmessage so you don't become a meal. >>
Well, I use Remailers since the early 90s and Bitmessage for a couple of years
now and I would not use Omnimix nor the original Bitmessage client for sensitive
things, to become not a meal, so to speak.[1]
Please check out my diagram.png[2] on GitHub and tell me what is bad about using Mixnetworks with Bitmessage, *if* the user creates outfiles with
YAMN or Mixmaster, on a second offline device, not connected to the
Internet, and transfers the outfile with a 3.5 inch disk to the online computer, where the user can then inject the outfile to a native mix client, in order to send it to a Bitmessage user or a chan?
That was the reason why I ran a mail2chan Gateway in the past. Wish
others would do the same and run a mail2chan Gateway again!
If the Bitmessage client, maybe a CLI Version, would allow us to create
BM payload offline and then inject it later via an online computer, well
that would be very very nice!!!
[1] I guess, since Pegasus and others appeared, a couple of years ago, everybody would agree that it may not be a wise decision to create
messages, for anonymous communications, directly on an online device.
[2] https://github.com/stefanclaas/mail2chan/blob/main/Diagram.png
On Sun, 19 May 2024 00:25:14 +0200
Stefan Claas <pollux@tilde.club> wrote:
<snip>
If the Bitmessage client, maybe a CLI Version, would allow us to create
BM payload offline and then inject it later via an online computer, well that would be very very nice!!!
One could encrypt the message with PGP on a air-gapped machine then transfer the PGP-encrypted ciphertext to the networked Bitmessage machine. Even better would be a secret shared key using a cascade of symmetric ciphers. In reality there would be
two 'addresses' per party: the Bitmessage address and the PGP key or secret cipher key.
Also it is very easy to dump a encrypted Bitmessage object from the messages.dat file, then import it on another machine. So one could run Bitmessage with keys on a air-gap machine to generate the message, dump the encrypted sqlite object, then
import that sqlite object on the connected machine (with no chan or address keys in keys.dat) and start up Bitmessage to let it connect to the network and synchronize.
It would not be difficult to write a command-line script to perform this sqlite swap, eliminating many of the individual steps.
There is also a command in the Bitmessage API to send a pre-encrypted Bitmessage payload. You would need to dig in the source code to see how it works.
Doesn't bitmessage have scalability issue? It's been years since I last looked into it, but doesn't it send every message to every node?
Also, is it still active? I remember seeing some security incident, and
then nothing happened with the client for a long time.
D wrote:
Doesn't bitmessage have scalability issue? It's been years since I last
looked into it, but doesn't it send every message to every node?
Correct, when a lot of people would use it and it sends to every node.
Also, is it still active? I remember seeing some security incident, and
then nothing happened with the client for a long time.
Well, yes it is still an active community, but not so big. About the incident, this was also fixed long ago. The client for Linux and Windows
is still being updatet, but you don't see it on the Wiki. I currently
do not have the download URLs handy.
On Sun, 19 May 2024, Stefan Claas wrote:
D wrote:
Doesn't bitmessage have scalability issue? It's been years since I last
looked into it, but doesn't it send every message to every node?
Correct, when a lot of people would use it and it sends to every node.
Also, is it still active? I remember seeing some security incident, and
then nothing happened with the client for a long time.
Well, yes it is still an active community, but not so big. About the incident, this was also fixed long ago. The client for Linux and Windows
is still being updatet, but you don't see it on the Wiki. I currently
do not have the download URLs handy.
Oh, that's interesting! Where does the community interaction take place? I've looked at the wiki and thought the project was dead. Glad to hear
that there's still some action! =)
D wrote:
On Sun, 19 May 2024, Stefan Claas wrote:
D wrote:
Doesn't bitmessage have scalability issue? It's been years since I last >>>> looked into it, but doesn't it send every message to every node?
Correct, when a lot of people would use it and it sends to every node.
Also, is it still active? I remember seeing some security incident, and >>>> then nothing happened with the client for a long time.
Well, yes it is still an active community, but not so big. About the
incident, this was also fixed long ago. The client for Linux and Windows >>> is still being updatet, but you don't see it on the Wiki. I currently
do not have the download URLs handy.
Oh, that's interesting! Where does the community interaction take place?
I've looked at the wiki and thought the project was dead. Glad to hear
that there's still some action! =)
You can find the bitmessage community in chan bitmessage. Last year was a posting
here which lists other chans.
<https://groups.google.com/g/alt.privacy.anon-server/c/uJmZM7x6JOo/m/b4isFyOYBAAJ>
You can of course create your own (private) chans, for communications with friends.
On Mon, 20 May 2024, Stefan Claas wrote:
D wrote:
On Sun, 19 May 2024, Stefan Claas wrote:
D wrote:
Doesn't bitmessage have scalability issue? It's been years since I last >>>> looked into it, but doesn't it send every message to every node?
Correct, when a lot of people would use it and it sends to every node. >>>
Also, is it still active? I remember seeing some security incident, and >>>> then nothing happened with the client for a long time.
Well, yes it is still an active community, but not so big. About the
incident, this was also fixed long ago. The client for Linux and Windows >>> is still being updatet, but you don't see it on the Wiki. I currently
do not have the download URLs handy.
Oh, that's interesting! Where does the community interaction take place? >> I've looked at the wiki and thought the project was dead. Glad to hear
that there's still some action! =)
You can find the bitmessage community in chan bitmessage. Last year was a posting
here which lists other chans.
<https://groups.google.com/g/alt.privacy.anon-server/c/uJmZM7x6JOo/m/b4isFyOYBAAJ>
You can of course create your own (private) chans, for communications with friends.
Hmm, pro-tip. If you want to grow bitmessage engagement, open a channel somewhere that doesn't need bitmessage in order to participate. Then it tends to become a channel preaching to the choir.
Or is there a web archive/interface somewhere as well? That would be nice! =)
Years ago there was beamstat.com, a web page where you could see and read all known
chans and posting to them was at the beginning also allowed, via the web-interface.
D wrote:
On Mon, 20 May 2024, Stefan Claas wrote:
D wrote:
On Sun, 19 May 2024, Stefan Claas wrote:
D wrote:
Doesn't bitmessage have scalability issue? It's been years since I last >>>>>> looked into it, but doesn't it send every message to every node?
Correct, when a lot of people would use it and it sends to every node. >>>>>
Also, is it still active? I remember seeing some security incident, and >>>>>> then nothing happened with the client for a long time.
Well, yes it is still an active community, but not so big. About the >>>>> incident, this was also fixed long ago. The client for Linux and Windows >>>>> is still being updatet, but you don't see it on the Wiki. I currently >>>>> do not have the download URLs handy.
Oh, that's interesting! Where does the community interaction take place? >>>> I've looked at the wiki and thought the project was dead. Glad to hear >>>> that there's still some action! =)
You can find the bitmessage community in chan bitmessage. Last year was a posting
here which lists other chans.
<https://groups.google.com/g/alt.privacy.anon-server/c/uJmZM7x6JOo/m/b4isFyOYBAAJ>
You can of course create your own (private) chans, for communications with friends.
Hmm, pro-tip. If you want to grow bitmessage engagement, open a channel
somewhere that doesn't need bitmessage in order to participate. Then it
tends to become a channel preaching to the choir.
Or is there a web archive/interface somewhere as well? That would be nice! >> =)
Years ago there was beamstat.com, a web page where you could see and read all known
chans and posting to them was at the beginning also allowed, via the web-interface.
Stefan Claas wrote:
Years ago there was beamstat.com, a web page where you could see and read >> all known chans and posting to them was at the beginning also allowed,
via the web-interface.
Maybe interesting for some of you.
If you right-click on your BM-address, on the left pane, you can get a
free Mailchuck email address from that Gateway.
It can then be used, for example, as a Remailer reply address,
or as email address for registering at WWW sites.
If you have BTC you can get a paid Mailchuck account, which allows sending emails, from within the BM-client.
| Sysop: | Thumper |
|---|---|
| Location: | Copperopolis, CA |
| Users: | 6 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 73:04:03 |
| Calls: | 129 |
| Calls today: | 1 |
| Files: | 4,897 |
| Messages: | 37,197 |
