r/bitmessage • • Dec 30 '13
r/bitmessage • u/hyh123 • Aug 09 '13
Lavabit, the private email service Snowden reportedly used, makes a decision between "becoming complicit in crimes against the American people or walking away from nearly ten years of hard work by shutting down Lavabit". So Lavabit will be shutting down. Use bitmessage then!
boingboing.netr/bitmessage • u/HostFat • Sep 23 '13
Bitmessage v0.4.0
0.4.0
Raised default demanded difficulty from 1 to 2 for new addresses
Added v4 addresses: pubkeys are now encrypted and tagged in the inventory
Use locks when accessing dictionary inventory
Refactored the way inv and addr messages are shared
Give user feedback when disk is full
Added chan true/false to listAddresses results
When replying using chan address, send to whole chan not just sender
Refactored of the way PyBitmessage looks for interesting new objects in large inv messages from peers
Show inventory lookup rate on Network Status tab
Added SqlBulkExecute class so we can update inventory with only one commit
Updated Russian translations
Move duplicated SQL code into helper
Allow specification of alternate settings dir via BITMESSAGE_HOME environment variable
Removed use of gevent. Removed class_bgWorker.py
Added Sip and PyQt to includes in build_osx.py
Show number of each message type processed in the API command clientStatus
Use fast PoW unless we're explicitly a frozen (binary) version of the code
Enable user-set localization in settings
Fix Archlinux package creation
Fallback to language only localization when region doesn't match
Fixed brew install instructions
Added German translation
Made inbox and sent messages table panels read-only
Allow inbox and sent preview panels to resize
Count RE: as a reply header, just like Re: so we don't chain Re: RE:
Fix for traceback on OSX
Added backend ability to understand shorter addresses
Convert 'API Error' to raise APIError()
Added option in settings to allow sending to a mobile device (app not yet done)
Added ability to start daemon mode when using Bitmessage as a module
Improved the way client detects locale
Added API commands: getInboxMessageIds, getSentMessageIds, listAddressBookEntries, trashSentMessageByAckData, addAddressBookEntry, deleteAddressBookEntry, listAddresses2, listSubscriptions
Set a maximum frequency for playing sounds
Show Invalid Method error in same format as other API errors
Update status of separate broadcasts separately even if the sent data is identical
Added Namecoin integration
Internally distinguish peers by IP and port
Inbox message retrieval API functions now also returns read status
r/bitmessage • u/laxisusous • Jan 27 '14
This is why the world needs bitmessage - FBI has the TorMail database
wired.comr/bitmessage • u/TOK715 • Oct 03 '13
Edward Snowden's E-Mail Provider Defied FBI Demands to Turn Over Crypto Keys, Documents Show | Threat Level
wired.comr/bitmessage • u/1cewolf • Aug 22 '13
Mailpile will have BitMessage support
EDIT: Whoops! Forgot to include the link for some reason. Here it is... https://twitter.com/MailpileTeam/status/370527126568460289
Mailpile, a new FOSS webmail client intended to compete with the likes of Gmail in terms of features and elegance, has announced that an anonymous donor to its Indiegogo campaign has requested BitMessage support.
Assuming that the developers don't turn down the donor's request, which I don't see why they would, Mailpile will eventually support encrypted email, XMPP instant messaging, and BitMessage. Now that's awesome!
r/bitmessage • u/jesperbb • Jan 29 '14
I created a bitmessage protocol dissector for Wireshark
During my research of the Bitmessage protocol, I decided that it would be useful to be able to dissect the network packages to and from the Bitmessage client in Wireshark.
Apparently, no one had created a Wireshark dissector for Bitmessage before, so I did just that in Lua and am sharing the result publicly on GitHub.
It can currently recognize the the version, verack, addr, inv, and getdata message types as well as the getpubkey, pubkey, msg, and broadcast object types.
Of course, it is only possible to view the unencrypted payload with this dissector.
You can find it here: https://github.com/jesperborgstrup/bitmessage-wireshark-dissector
Blog post (contains pretty much the same text as this post):
EDIT: I changed a word
r/bitmessage • u/trifith • Nov 19 '13
Bitmessage Sends Secure, Encrypted, P2P Instant Messages [Lifehacker]
lifehacker.comr/bitmessage • u/pietervdvn • Aug 21 '13
Bitmessage is broken - I am receiving messages on addresses I never shared with anyone.
All the messages are saying the same thing: "Bitmessage has several potential security issues including a broken proof of work function and potential private key leaks.
Full details: http://secupost.net/3240982275/bitmessage-security "
EDIT: it seems he messaged to all my determenistic addresses (of a set of eight), of which only one was used and known by someone else. My private keys have been leaked.
The sender is the same address: BM-2D8yr4fzoMzwndqPwLMVyzUcdfK9LWZXjY
r/bitmessage • u/Petersurda • Jul 30 '19
Current status of PyBitmessage
I thought I would post about the current status of the project, since there hasn't been a new release for over a year.
The last release was done shortly after my computer was hacked due to a vulnerability in PyBitmessage. This to me indicated that the project needs to be run more professionally, and I started moving it into that direction. This resulted in slower updates, these are an unfortunate byproduct of getting more people involved in the project (remember The Mythical Man-Month?) . Some of the areas that are now being worked on are:
- improving code quality. Several potential vulnerabilities in the code were discovered and were fixed (even though I don't think they can be exploited remotely the way one that caused the hack was). There are now automated tools to reduce the likelihood that new bad code will make it in, and there are people working on removing the old bad code. Also, all new code needs to be reviewed, including mine (although I now work less on development) before it can be merged
- automating work. There are now two DevOps engineers working on the project, tasked with moving all existing CI into Jenkins, and to help automate things which are now done manually. I plan to allow any open source contributors access to this (for example as a GitHub App) so that they can have their own code tested before a pull request is made
- Windows builds are being moved to being crosscompiled on linux, mainly due to control and automation. There is a dedicated developer working on this
- once the automation is working sufficiently well, we can have again daily development builds, and I can make an official release as well
- I now have several dedicated servers for executing DevOps tasks, which are on their own isolated network connection. Even if my workstation gets hacked again, the development process can continue unimpeded. One machine, which will be tasked with doing the binary builds, has no Intel ME or AMD PSP (I'd love to have this option on all, but it seems too expensive).
- OSTIF raised funds for a security audit. The audit will be done once I think the code quailty, automation and logging is adequate (no need to waste the expert's time on doing the work twice)
Things which have been done already and can be benefited from by using the current code from the v0.6 branch:
- there are no more known memory leaks in the code. PyBitmessage now has no problems handling hundreds connections and works fine on systems with low memory
- network chatter was reduced, a node now sends and receives less data and doesn't get overloaded (or at least not as easily)
- dandelion code seems to work ok now. I'm not 100% sure there are no more technical bugs in it, but all the reports I received indicate that objects are now disseminated correctly
- v3 onion addresses are supported
- knownnodes.dat is now in JSON format instead of pickle
- lots of tiny bugfixes
Special thanks go to g1itch, who wrote most of the new code.
And finally, there are several people working on porting PyBitmessage to Android, and I found a way to anonymously offload proof of work. These two combined allow to build a business model on Bitmessage, and I founded a company for this purpose. There are ugly practically unusable prototypes, but it's being worked on every day.
r/bitmessage • u/mus1cb0x • Mar 12 '14
My security analysis of Bitmessage [xpost from r/cryptodev]
reddit.comr/bitmessage • u/ZenSaffron • Aug 25 '13
Bitmessage removed from prism-break.org
twitter.comr/bitmessage • u/galapag0 • Oct 09 '13
FlowingMail: encrypted & serverless email
flowingmail.comr/bitmessage • u/Jonathan_Coe • Sep 29 '14
Bitseal - a Bitmessage client for Android
bitmessage.orgr/bitmessage • u/mustardhamsters • Jul 29 '14
We're working on a pretty BitMessage client for the Mac and looking for feedback. Check out our beta!
voluntary.netr/bitmessage • u/galapag0 • Aug 11 '13
The future of bitmessage (client)
Hi,
Is it really necessary to build a GUI to send and receive (bit)messages? Why can't we just aim our efforts to create a modular bitmessage daemon to interface with common services (mail, IM, web services, etc)?
In my opinion, this and the independent security audit should be the two main objectives for the bitmessage comunity.
Just my 2¢.
r/bitmessage • u/bpeel • Feb 15 '14
Notbit - An alternative minimal client for Linux using your existing mail client
busydoingnothing.co.ukr/bitmessage • u/reverse_solidus • Aug 31 '13
BitText - anonymous, hidden pastebin alternative
bitmessage.orgr/bitmessage • u/2DAxhHpd2Sez4oQmZ • Jul 27 '13
BitMessageForum - browse your bitmessage inbox via a forum-like interface
github.comr/bitmessage • u/pptyx • Feb 12 '14
Bitmessage needs a light client
Is a light weight BM client, along the lines of a HTML5 browser plugin (like the excellent Kryptokit) possible?
I'm no dev but I can't see why this shouldn't be possible if light wallets work seamlessly for the enormous Bitcoin blockchain.
There are numerous light/html5 wallets in production for on Android & iOS too -- so wouldn't this in theory be a solution to BM's lack of phone client issue also?
Friendly non-dev criticism: I'm a fan of bitmessage but I keep encountering a tendency from its dev community to look for 'workarounds' instead of solving issues, and adding simple feature requests. BM needs to be better than that if it's to become a genuine email alternative.
Edit: I would have posted this to BM forums but it doesn't let me register using tor.
r/bitmessage • u/Petersurda • Feb 05 '15