There has been a lot of drama in the MRC scene as of late. People have been having serious conversations as to how MRC should go down the line... whether chat rooms are to be considered secure or totally open. Anyhow, MeaTLoTioN has implemented a new cryptographic scheme into MRC so that PrivMsgs can be thought of as at least marginally more secure than what it was before. MeaTLoTioN has the programming skill to make secure messaging a thing. He is the person with the skills and connections to the MRC Dev people so that he can actually make this thing happen. Check back at the new time for the weekly meetup at 7pm Eastern Time and ask around to see what's going on. Actually even better than the Friday night meetup would be the Matrix/Element server at https://elements.erb.pw. I could be wrong with the address, it might be element.erb.pw, but one of those two will work. As with anything to do with cryptography I'd advise that you look at the code before putting your full trust in it, but at the very least this will stop the trolls who do dragnet collection of all MRC traffic, and literally that is what has been happening, some times people would be talking in the /msg [username] [content] format and PrivMsgs were sent, but then the person who was being talked about then confronts people with exactly what was being said in "private." PrivMsgs is NOT private. I'd be willing to receive the code to MRC into a message on Sp00knet so we can all look it over.

Cheers!
-warmfuzzy

P.S. I should also mention that mrcX is implementing some pseudo-cryptography in the new MRC client called mrcX. It is not what I'm talking of here. mrcX is using pseudo crypto (in simple terms very simple crytpo) that will have your chat safe from big brother but not big government.

Props to ML for his leet code
-wf

--- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (700:100/37)

On 22 Mar 2023, warmfuzzy said the following...

Anyhow, MeaTLoTioN has implemented a new cryptographic scheme into MRC
so that PrivMsgs can be thought of as at least marginally more secure
than what it was before. MeaTLoTioN has the programming skill to make secure messaging a thing. He is the person with the skills and connections to the MRC Dev people so that he can actually make this
thing happen. Check back at the new time for the weekly meetup at 7pm

So is this coming in the form of a client, the backend or both?

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |20|15Radio|10@|14HTTP://Noverdu.com:88
|16|10 Standard ports for SSH/Telnet |04 WEB|14@|12HTTP://noverdu.com:808 |20|15Global Chat, Global Messaging and Games! |16|10Ditch the Unsocial Media

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (700:100/84)

On 22 Mar 2023, warmfuzzy said the following...

There has been a lot of drama in the MRC scene as of late. People have been having serious conversations as to how MRC should go down the
line... whether chat rooms are to be considered secure or totally open. Anyhow, MeaTLoTioN has implemented a new cryptographic scheme into MRC
so that PrivMsgs can be thought of as at least marginally more secure

As the present MRC uses stackfault's servers, rather than Meatlotion's, will these two efforts be unified. Stackfault has also announced a series of MRC V2 features in an effort to make the experience less a wild west adventure.

Additionally Roovis previously successfully demonstrated encrypted private messages as part of the mrcX project, where the server end never apparently has an unencrypted copy, but rather the encryption was client to end client.

Seems there is at least three overt approaches competing.

Might be a while for some harmony?

--- Steve K9ZW via SPOT BBS

--- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
* Origin: SPOT BBS / k9zw (700:100/69)

warmfuzzy wrote to All <=-

Anyhow, MeaTLoTioN has implemented a new cryptographic scheme into MRC
so that PrivMsgs can be thought of as at least marginally more secure
than what it was before. MeaTLoTioN has the programming skill to make secure messaging a thing. He is the person with the skills and connections to the MRC Dev people so that he can actually make this
thing happen. Check back at the new time for the weekly meetup at 7pm Eastern Time and ask around to see what's going on.

There are quite a few of us, I think, using the Synchronet MRC client -
it's something that echicken hacked together about a year ago. It'd be
good to get any information echicken would need to update the Sync
client if changes are afoot.

I think he did it for grins, and doesn't use it much, so it's possible
it's not on his radar.




... Filters, the sublime elevation of the lifter and the filters
--- MultiMail/Win v0.52
* Origin: realitycheckBBS.org -- information is power. (700:100/20)

As the present MRC uses stackfault's servers, rather than Meatlotion's, will these two efforts be unified. Stackfault has also announced a
series of MRC V2 features in an effort to make the experience less a
wild west adventure.

No matter what, all this is bad news for MRC. Way to go, community.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: 2o fOr beeRS bbS >> 20ForBeers.com:1337 (700:100/71)

So meatlotion has his own server going now? I want to know that address. I will add a choice to the chat menu. What is the new address?

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |20|15Radio|10@|14HTTP://Noverdu.com:88
|16|10 Standard ports for SSH/Telnet |04 WEB|14@|12HTTP://noverdu.com:808 |20|15Global Chat, Global Messaging and Games! |16|10Ditch the Unsocial Media

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (700:100/84)

So meatlotion has his own server going now? I want to know that
address. I will add a choice to the chat menu. What is the new address?

Its on Quantum Wormhole and is closed, mainly, to bbSes... one could email MeaTLoTioN, tho.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: 2o fOr beeRS bbS >> 20ForBeers.com:1337 (700:100/71)

There are quite a few of us, I think, using the Synchronet MRC client -
it's something that echicken hacked together about a year ago. It'd be
good to get any information echicken would need to update the Sync
client if changes are afoot.

I think he did it for grins, and doesn't use it much, so it's possible it's not on his radar.

I digged into Enigma and Synchronet clients and can make the required adjustments if need be. I always prefer when the maintainers get involved tho.

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (700:100/33)

There has been a lot of drama in the MRC scene as of late. People have been having serious conversations as to how MRC should go down the
line... whether chat rooms are to be considered secure or totally open.

There is change already happening in MRC.

1. Routing of messages is now deterministic. Only the right board gets he message.
2. Rooms can now be secured (except lobby) so you can carry conversation in smaller groups.
3. Encryption will come very soon as I'm working on a release to address some smaller issues, all compatible with version 1 of MRC while I finish the v2 implementation.

More to come.

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (700:100/33)

As the present MRC uses stackfault's servers, rather than Meatlotion's, will these two efforts be unified. Stackfault has also announced a
series of MRC V2 features in an effort to make the experience less a
wild west adventure.

Well, looks like ML decided to go on it's own, maybe he'll come back one day.

However, massive efforts are now being put into MRC and more to be announced for sure.

Additionally Roovis previously successfully demonstrated encrypted
private messages as part of the mrcX project, where the server end never apparently has an unencrypted copy, but rather the encryption was client to end client.

The intent is to have encryption at several levels. Room level and client level, depending on the case.

Seems there is at least three overt approaches competing.

Hopefully things will get better.


Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (700:100/33)

As the present MRC uses stackfault's servers, rather than Meatlotion' will these two efforts be unified. Stackfault has also announced a series of MRC V2 features in an effort to make the experience less a wild west adventure.

No matter what, all this is bad news for MRC. Way to go, community.

This is the plan, but the larger community. This is gonna be fun.

Cheers!

|15 ß Þ |15StackFault |08<|03.|11.|15P|11h|03EN|11o|15M|11.|03.|08>
|11 Ý ß |11The Bottomless Abyss BBS
|03 ß Ýß |03ssh|08.|072222 |08/ |03telnet|08.|072023 |08/ |03https
|08 ÜþÞ |08bbs|07.|08bottomlessabyss|07.|08net

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: The Bottomless Abyss BBS * bbs.bottomlessabyss.net (700:100/33)