Welcome, Guest. Please login or register.

Poll

Do you want to see this implemented?

Yes
17 (65.4%)
Change it
3 (11.5%)
No
6 (23.1%)

Total Members Voted: 20

Author Topic: Inclusion of Bitmessage adresses in DNS  (Read 10875 times)

AyrA

  • BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1261
  • Karma: +75/-7
  • bitmessage.ch and timeservice operator
    • View Profile
    • AyrAs Homepage
Inclusion of Bitmessage adresses in DNS
« on: July 26, 2013, 02:35:37 AM »
This is a quick draft, that proposes Bitmessage Address inclusion in Domain names without affecting the existing DNS structure. Implementation is as simple as possible.
The way bitmessage works is not changed. If a user enters a DNS Name, the address is looked up (if this feature is enabled in the settings) and is dynamically replaced in the background. A message is technically still sent to a Bitmessage address and not to a DNS replacement of it.
Examples use the Name "ayra.ch".
TXT Records have been set up for users to try out.

This proposes 2 record types, the general record and the specific record.

Format of general record
a TXT Record is created with the name bm.ayra.ch.
The content is:
Code: [Select]
[label=]address[;[label=]address[;...]]Example:
Code: [Select]
BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp;Timeservice Broadcast=BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash;24x7 Mailing List=BM-GuRLKDhQA5hAhE6PDQpkcvbtt1AuXAdQ
The sub-domain is always "BM".
The general record is used to store multiple addresses. The user can subscribe these or add them to the address book. if he sends a message to the general record, he has to choose which address he wants in case multiple exist. Instead of chaining Addresses together, multiple TXT records can be set.
This record serves as an introduction purpose. It does not needs to exist if users want to have a specific record.

Format of specific record
a TXT Record is created with the name list.ayra.ch.
The content is:
Code: [Select]
[label=]addressExample:
Code: [Select]
24x7 Mailing List=BM-GuRLKDhQA5hAhE6PDQpkcvbtt1AuXAdQ
The subdomain can be any valid DNS subdomain value.
A domain can have multiple specific records.
The specific record can only contain one address and is meant to be used as destination address. So instead of people using "BM-GuRLKDhQA5hAhE6PDQpkcvbtt1AuXAdQ", they send a message to "list.ayra.ch"

Proof of concept
A working PHP script can be found here: http://home.ayra.ch/dns.php
« Last Edit: July 30, 2013, 03:54:04 AM by AyrA »
My Address: BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
Bitmessage Time Service (Subscribe): BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash
Support the Multipart Message Declaration Draft for Bitmessage: https://bitmessage.org/forum/index.php/topic,1553.0.html
Free Bitmessage to E-Mail Gateway: https://bitmessage.ch

neko259

  • Newbie
  • *
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #1 on: July 26, 2013, 10:23:04 AM »
I don't think that give human-readable addresses only for people who have a domain is a good idea (if I understood the idea right).
BM-GuDb9g2fuaCGbShKrUNUUFQkaCYJfUNv

AyrA

  • BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1261
  • Karma: +75/-7
  • bitmessage.ch and timeservice operator
    • View Profile
    • AyrAs Homepage
Re: Inclusion of Bitmessage adresses in DNS
« Reply #2 on: July 26, 2013, 01:51:06 PM »
a domain can host unlimited number of addresses. So I could open a website, where you can register with a username and a password, then set your Address. you would then get a subdomain XYZ.bitmessage.ch where XYZ is your username.
My Address: BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
Bitmessage Time Service (Subscribe): BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash
Support the Multipart Message Declaration Draft for Bitmessage: https://bitmessage.org/forum/index.php/topic,1553.0.html
Free Bitmessage to E-Mail Gateway: https://bitmessage.ch

Jaxkr

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +1/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #3 on: July 26, 2013, 07:56:52 PM »
This is a fantastic idea! And it shouldn't give addresses away because a third party can't get a completely list of your domain's subdomains.

nimda

  • Full Member
  • ***
  • Posts: 161
  • Karma: +12/-2
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #4 on: July 26, 2013, 09:20:29 PM »
This does create an attack vector. If you securely give someone a Bitmessage address which you securely generated, and they send you a message from a secure machine, then (in theory), only you can read the message. However if you securely give someone a DNS lookup, the registrar and presumably one or more governments can alter the address.

(I voted yes)
It's 90% UI from here. uPnP is a must.
BM-2DARKo7LcCvBiXyyabT5vNxgQ32pBqScuk

Jaxkr

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +1/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #5 on: July 26, 2013, 10:06:45 PM »
This does create an attack vector. If you securely give someone a Bitmessage address which you securely generated, and they send you a message from a secure machine, then (in theory), only you can read the message. However if you securely give someone a DNS lookup, the registrar and presumably one or more governments can alter the address.

(I voted yes)
There could be some form of signing in the txt record to prevent this.

dokument

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 488
  • Karma: +37/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #6 on: July 27, 2013, 12:15:08 AM »
Excuse my ignorance but what would this change with bitmessage itself?
BM-2cTtoitr47Q7weyKr9pFX363YBRMQfBWzt

Jaxkr

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +1/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #7 on: July 27, 2013, 12:43:18 AM »
Excuse my ignorance but what would this change with bitmessage itself?
The version I'm working on is.
It follows this logic.
1. Is it a valid BM address? If so, carry on to message sending.
2. Is it a valid URL with a txt record containing an address?
3. If so, get the Bitmessage address from a TXT record in the domain.
4. Send the message using the recieved address.
5. Add the address to contacts with the label in the TXT record.

srmojuze

  • Full Member
  • ***
  • Posts: 155
  • Karma: +6/-0
    • View Profile
    • BitChirp.org
Re: Inclusion of Bitmessage adresses in DNS
« Reply #8 on: July 27, 2013, 08:03:02 AM »
Very interesting.

AyrA

  • BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1261
  • Karma: +75/-7
  • bitmessage.ch and timeservice operator
    • View Profile
    • AyrAs Homepage
Re: Inclusion of Bitmessage adresses in DNS
« Reply #9 on: July 27, 2013, 08:07:22 AM »
There could be some form of signing in the txt record to prevent this.
The solution to this is DNSSEC and its almost free to use for domain holders.
My Address: BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
Bitmessage Time Service (Subscribe): BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash
Support the Multipart Message Declaration Draft for Bitmessage: https://bitmessage.org/forum/index.php/topic,1553.0.html
Free Bitmessage to E-Mail Gateway: https://bitmessage.ch

Jaxkr

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +1/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #10 on: July 27, 2013, 01:20:14 PM »
There could be some form of signing in the txt record to prevent this.
The solution to this is DNSSEC and its almost free to use for domain holders.
Thanks for the info. This could be optionally supported.

dokument

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 488
  • Karma: +37/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #11 on: July 27, 2013, 09:57:01 PM »
The version I'm working on is.
It follows this logic.
1. Is it a valid BM address? If so, carry on to message sending.
2. Is it a valid URL with a txt record containing an address?
3. If so, get the Bitmessage address from a TXT record in the domain.
4. Send the message using the recieved address.
5. Add the address to contacts with the label in the TXT record.
But how would that change the bitmessage protocol itself?

Also wouldn't this be a great list to spam from...
BM-2cTtoitr47Q7weyKr9pFX363YBRMQfBWzt

Jaxkr

  • Jr. Member
  • **
  • Posts: 62
  • Karma: +1/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #12 on: July 27, 2013, 10:05:50 PM »
The version I'm working on is.
It follows this logic.
1. Is it a valid BM address? If so, carry on to message sending.
2. Is it a valid URL with a txt record containing an address?
3. If so, get the Bitmessage address from a TXT record in the domain.
4. Send the message using the recieved address.
5. Add the address to contacts with the label in the TXT record.
But how would that change the bitmessage protocol itself?

Also wouldn't this be a great list to spam from...
No. It wouldn't change the Bitmessage protocol itself at all.
What do you mean list to spam from? Getting a list of BM domains is no easier than getting a list of BM addresses.

akh81

  • Newbie
  • *
  • Posts: 10
  • Karma: +0/-0
    • View Profile
Re: Inclusion of Bitmessage adresses in DNS
« Reply #13 on: August 02, 2013, 07:49:11 PM »
I respect the efforts that the authors of the proposal put into it, but voted "No".

At the end of the day, Bitmessage is an encrypted and anonymous email. The rest is bells and whistles.

One can think of numerous attack vectors that will be introduced by going this direction (I am with "nimda" here).
Say, can you spot any difference between the following two "addresses"?
ayra.ch
ауrа.сh

Hint: these two addresses are different in 4 characters out of 7.

Also, how about innocent typos in "To:" field?
if one creates an address "occasional.ch"
certain percentage of people will necessarily type it as "occassional.ch" or "occasanal.ch" introducing a potential leak.

It really feels like a wrong direction to go for the software that's main proposition is encryption and anonymity.
« Last Edit: August 02, 2013, 08:17:07 PM by akh81 »
BM-GttZLBeZSzg1fxvuDRJnqLgLHRTaKsyE

AyrA

  • BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1261
  • Karma: +75/-7
  • bitmessage.ch and timeservice operator
    • View Profile
    • AyrAs Homepage
Re: Inclusion of Bitmessage adresses in DNS
« Reply #14 on: August 03, 2013, 05:29:00 AM »
Say, can you spot any difference between the following two "addresses"?
ayra.ch
ауrа.сh
It does not matters, if the writing is different. Users are gonna type it anyways manually. If they copy paste it, they get the issue, that the second ayra.ch actually translates to xn--r-7sbb8e.xn--h-6tb and exactly this translation needs to be done manually by bitmessage itself and I doubt that it will be implemented apart from the fact, that the TLD is invalid. I recommend reading DNS specs first and you will see, that you can (still) only submit true ASCII request to a conform DNS server. So if somebody enters an UTF-8 name, he simply get a not found. For everybody sticking to the ISO language norms (like me) the domain name just apperas as a bunch of squares.

Assuming the translation is included:
To solve this issue, the client can display the DNS name after resolution like: name (BM-Whatever) in the field. A user then will easily see, that the "name" suddenly isn't ayra.ch but is xn--r-7sbb8e.xn--h-6tb instead.

Also, how about innocent typos in "To:" field?
if one creates an address "occasional.ch"
certain percentage of people will necessarily type it as "occassional.ch" or "occasanal.ch" introducing a potential leak.
This issue is not DNS specific, it works with bitmessage addresses as well. Mistyping BM addresses is even more likely because proper casing matters. Theoretically there can be two bitmessage addresses, that just differ in one char.

It really feels like a wrong direction to go for the software that's main proposition is encryption and anonymity.
Thinking about it, windows in buildings are also wrong. People can jump out and hurt or even kill themselves.

You do not need to use it if you do not want. If you show bitmessage to somebody they generally like it until they see the addresses.
The DNS inclusion can help people get started with bitmessage and get some addresses they can communicate with and listen to broadcasts. If they really want to communicate anonymously, they will get the address directly from the person they want to talk to.
« Last Edit: August 03, 2013, 05:31:11 AM by AyrA »
My Address: BM-Bc7Rspa4zxAPy9PK26vmcyoovftipStp
Bitmessage Time Service (Subscribe): BM-BcbRqcFFSQUUmXFKsPJgVQPSiFA3Xash
Support the Multipart Message Declaration Draft for Bitmessage: https://bitmessage.org/forum/index.php/topic,1553.0.html
Free Bitmessage to E-Mail Gateway: https://bitmessage.ch