Please make an Android app once the desktop apps are done. And please release the Android app on F-Droid so degoogle Android users can download the app.

Please add a feature to have a Wahay overlay in games. The Mumble overlay is a great overlay that works. This will make Wahay a good gaming voice chat since Wahay does not require a server like Mumble and Mumble servers cost money and Discord has poor privacy.

Gaming Overlay in games
Overlay hotkey (A setting to choose the overlay hotkey)
Overlay shows who is talking

hi, dear team wahay

i have the installed version: 0.0~git20200605.d3f0d21-1

I am using Debian Buster and I installed wahay via repository:

/etc/apt/sources.list.d/wahay.list

deb https://dl.autonomia.digital/debian buster main
deb-src https://dl.autonomia.digital/debian buster main

the software is working great, thanks

but today i realized that when I am updating my repos the following error appears:

E: The repository 'https://dl.autonomia.digital/debian buster Release' no longer has a Release file.

thanks in advance

Does this project work well on windows (both build and run)?

Steps to reproduce

1. Install the onion-grater profile into Whonix-Gateway.
2. Run Wahay on Whonix-Workstation.
3. Host a meeting.
4. Join your own meeting.

Expected results

Mumble should connect.

Observed results

Mumble says Server connection failed: Connection refused.

Other notes

This is because the Tor daemon is receiving an IP of 0.0.0.0 for the ADD_ONION event, thus it's forwarding the incoming onion service connections to the wrong IP.

The conference URLs are ephemeral and exist only for the time of the meeting. This makes it harder for someone to get into a meeting without being invited.

Certainly a valid viewpoint.

However, constantly re-creating sessions is tedious. Then one also has to always re-share the secret join link over a pre-secure channel. And due to usability issues, many users are short of pre-secure channels.

For me, it's much more convenient to once set up a messenger and then have something like a contract list where people can be re-contacted later.

There's also currently as far as I know no onion to onion messenger. (TorChat was but was abandoned, never got onion v3 support.)

Could you please consider extending wahay to become a chat (re-using mumble chat feature)?

Hello , Have you fixed this issue on grumble ( ocb2.go ) :
https://github.com/mumble-voip/mumble/pull/4720

Thank you .

Mumble normally has a group chat that allows people to write during a meeting. This is useful when some has issues with audio, or to ask questions without interrupting the speaker. However this chat function is not working in Wahay, you can only do one on one chats.

Looking at https://wahay.org/download.html it says alot of headache to support multiple Linux distros, Well the solution is simple by just having 1 image for all of the distros through https://appimage.org/ and some advantages of having that are:

• No need multiple builds for multiple distros
• Support inline-upgrade (No need to download the new releases by checking the main website over and over) (check https://docs.appimage.org/packaging-guide/optional/updates.html , https://github.com/AppImage/AppImageUpdate )
• Run within user privileges/read-only (No installation required which is a security benefit since no root needed)
• Support sandboxing (Probably not straight forward without issues e.g #550 , #839 , #452)

In this instruction:

https://wahay.org/documentation/getting-started/installation/#debian-and-ubuntu

it only recommend to install curl, but later we find this command:

echo deb https://dl.autonomia.digital/debian $(lsb_release -c | cut -f 2) main | sudo tee /etc/apt/sources.list.d/wahay.list

This wont work as well, because lsb-release and apt-transport-https packages are not installed by default. (in debian similar to curl)

So to fix this in the first command we should add:

sudo apt install curl lsb-release apt-transport-https

Wahay can't start, can be reproduced following:

Wahay installed 08.06.2020 from
https://wahay.org/downloads/wahay-latest :

Wahay (commit: d3f0d21 (d3f0d21) tag:
(no tag) built: 2020-06-05 00:19:30)

manually installed dependencies:

• mumble 1.3.0-9
• xclip-0.13-3
• tor-0.4.3.5-2

OS: Parabola Linux (libre version of archlinux)

Steps to reproduce:

1. run: ./wahay-latest
2. Host meeting
3. Fill meeting screen and click "Start Meeting"
   → if "Automatically join meeting" is set, gets Error screen.
   → if "Automatically join meeting" is not set, gets "Now you are hosting
   a meeting" screen, and gets Error screen on "Join".

Sample stdout for hosting meeting without password:
./wahay-latest

INFO[0000] Detected language: en
INFO[0000] Using Tor binary found in: /usr/bin/tor
INFO[0000] Saving the config file to:
/home/user/.local/share/wahay/tor008621676/torrc INFO[0007] Using
Mumble located at: /tmp/mumble897446107/mumble INFO[0007] Using Mumble
environment variables: [] time="2020-06-08T23:29:05+02:00" level=info
msg=Grumble time="2020-06-08T23:29:05+02:00" level=info msg="Using data
directory: /tmp/wahay344371838" [1] 2020/06/08 23:29:24.909220 Started:
listening on 127.0.0.1:13300 INFO[0055] Storing Mumble client
certificate digest=08154c7de67b2713c87920a0aa07c6cf7a3f755f
hostname=whvdbykiz2tvyt72xnlxmlm5qyl5gyo5dicqr4masgtrbx6pwdozn6yd.onion
port=64738 ERRO[0056] joinMeetingHost() error: error: the service can't
be started INFO[0056] reportError(we couldn't start the meeting)

Process screens attached.

I tried to set debug option from settings, but no specific log file is
created or saved under indicated location. The same happens when
running ./wahay-latest --log /home/user/.config/wahay.log → no log
created.

I tried with tor service running and stopped, makes no difference
neither.

The vendored torgo dependency was last updated in this repo in 2019. Upstream has since merged some improvements (specifically wybiral/torgo#3 and wybiral/torgo#4) that would be helpful for running Wahay under Whonix. Any chance the vendored torgo could be bumped to latest from upstream?

Hi. Google released Lyra, a video codec that is supposed to work over very low bandwidth connections like 56K dial-up connections. I wonder if it can be integrated to accomplish low latency video conferencing over Tor. Would be very cool :)

https://www.phoronix.com/scan.php?page=news_item&px=Google-Lyra

Hi,

I built wahay from source and when I try to run wahay without mumble or Tor installed I got this screen:

which seems broken to me

Can't download https://dl.autonomia.digital/debian/keys.asc with curl as the TLS certificate did not have dl.autonomia.digital

Installation instructions for Debian and Ubuntu are unusable.

Expected Behavior

When running $ make gen-ui-locale on root folder the execution should succeed generating file /gui/catalog/catalog.go using lang files in /gui/locales (ar, en, es, ...).

Actual Behavior

The command $ make gen-ui-locale exits with errors :

cd gui && make generate-locale
make[1]: Entering directory '/home/[username]/go/src/github.com/[username]/wahay/gui'
# This beautiful code is necessary because gotext
# will barf if the golang.org/x/text/message package
# exists in the vendor directory when running...
# The world of programming is beautiful
rm -rf ../vendor/golang.org/x/text
go generate -x i18n.go
gotext -srclang=en update -out=catalog/catalog.go -lang=en,es,sv,ar,fr
/home/[username]/go/src/github.com/[username]/wahay/gui/i18n.go:23:28: cannot use tag (variable of type language.Tag) as language.Tag value in argument to message.NewPrinter
gotext: extract failed: : : couldn't load packages due to errors: github.com/[username]/wahay/gui
i18n.go:3: running "gotext": exit status 1
Makefile:2: recipe for target 'generate-locale' failed
make[1]: *** [generate-locale] Error 1
make[1]: Leaving directory '/home/[username]/go/src/github.com/[username]/wahay/gui'
Makefile:26: recipe for target 'gen-ui-locale' failed
make: *** [gen-ui-locale] Error 2

Steps to Reproduce the Problem

1. Fork https://github.com/digitalautonomy/wahay on GitHub
2. go get your fork (ex : https://github.com/[username]/wahay)
3. cd to your fork location (ex: ~/go/src/github.com/[username]/wahay)
4. Verify that make build runs without problems from root folder
5. Execute make gen-ui-locale

Specifications

Version: current
OS: Ubuntu 18.04
IDE: Visual Studio Code 1.45.1

Additional information

• The command runs without problems when working on main repository
• When on main repository folder, my IDE (vscode) shows no warning ; but when working on fork repository folder I get this highlight in file i18n.go on line 23:
  i18n = message.NewPrinter(tag, message.Catalog(message.DefaultCatalog))

cannot use tag (type "github.com/digitalautonomy/wahay/vendor/golang.org/x/text/language".Tag) as type "github.com/[username]/wahay/vendor/golang.org/x/text/language".Tag in argument to message.NewPrinter

Torsocks is usually installed by the Tor package on most platforms. Arch seems to be different in this regard. We should add an explicit check for the torsocks binary separate from the tor binaries to Wahay, and give a useful error to the user if torsocks is not found, something like "torsocks is not
installed, be sure to install this package in your distribution".

Hi,

I'm getting this error when I try to run wahay when I have mumble installed via apt on Debian12:

bin/wahay
INFO[0000] Detected language: en                        
INFO[0000] Using Tor binary found in: /usr/bin/tor      
INFO[0000] Saving the config file to: /home/m34n/.local/share/wahay/tor3896519667/torrc 
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x60 pc=0xc1aa78]

goroutine 21 [running]:
os/exec.(*Cmd).Output(0x3?)
	/usr/lib/go-1.19/src/os/exec/exec.go:675 +0x18
github.com/digitalautonomy/wahay/client.isThereAnAvailableBinary({0xc000542010, 0xf})
	/home/m34n/src/tahnous/src/wahay/client/binary.go:323 +0x3e2
github.com/digitalautonomy/wahay/client.searchBinaryInSystem()
	/home/m34n/src/tahnous/src/wahay/client/binary.go:290 +0x46
github.com/digitalautonomy/wahay/client.searchBinary(0x0?)
	/home/m34n/src/tahnous/src/wahay/client/binary.go:190 +0xa3
github.com/digitalautonomy/wahay/client.InitSystem(0x0?, {0x105f590?, 0xc0002fa000})
	/home/m34n/src/tahnous/src/wahay/client/client.go:66 +0xb3
github.com/digitalautonomy/wahay/gui.(*gtkUI).ensureMumble.func1.1()
	/home/m34n/src/tahnous/src/wahay/gui/mumble.go:18 +0x85
created by github.com/digitalautonomy/wahay/gui.(*gtkUI).ensureMumble.func1
	/home/m34n/src/tahnous/src/wahay/gui/mumble.go:15 +0xb8`

Checking here:

https://wahay.org/documentation/getting-started/installation/#debian-and-ubuntu

I can only see TLS version of the repository , TLS with Clearnet its for surely better than using http plain connection but TLS has its own issues (like MITM through SSL-Strip) so as the clearnet like exposing metadata of the connection and DNS issues...

For the website to be on the hidden services this to insure the anonymity for the user and the security when downloading or visiting wahay.

I setup the server on Debian 10. Everything setup correctly and i launched the server.

I downloaded Mumla from F-Droid to both a Pixel 4a with GrapheneOs and Pixel 3 with CalyxOS.

On both devices i successfully connected to the Wahay server via Orbot.

Everything looks fine no errors you just hear anything. I tried talking from the PC and verified the mic is working and receiving the input via Audio Statistics.

No audio came through on any of the devices. I also tried communicating audio from the mobile devices and none of those worked either.

I have setup Mumble as a hidden service using the whonix guide and that worked up until a few months i go i think system updates broke it.

Wahay is for sure not working despite everything looking good i see no obvious sign of error to explain why audio is not being transmitted.

I will add the Brazilian locale.

Generally, the locale code for brazilian portuguese is pt-br. Any opposition for adding it at pt-br? Might as well be just pt.

Please make an iOS app once the desktop apps are done.

Based on

Hi,

It seems that the repository for Debian Buster is not working.

My log

Ign:19 https://dl.autonomia.digital/debian buster InRelease
Err:20 https://dl.autonomia.digital/debian buster Release
  404  Not Found [IP: 185.108.76.90 443]
E: The repository 'https://dl.autonomia.digital/debian buster Release' no longer has a Release file.
N: No se puede actualizar de un repositorio como este de forma segura y por tanto está deshabilitado por omisión.

Thanks!

Hi,

It's my first time here.

My setup

• Debian 10
• Wahay-debian-10-2020-03-10-85a2c28

Dependency message:

"No se pudieron encontrar codecs CELT adecuados para los otros clientes. No podrá hablar a todos los usuarios"

Thanks, Jacobo

Checking the website security configurations through:

• https://www.hardenize.com/report/wahay.org/1614942638
• https://www.ssllabs.com/ssltest/analyze.html?d=wahay.org
• https://securityheaders.com/?q=https%3A%2F%2Fwahay.org%2F&followRedirects=on (F)

Website TLS/DNS/Headers... need to have alot of improvements hope these reports show where/what work need to be done.

I've created an Arch Linux package in the AUR for (easy)wahay install.

Package here: aur.archlinux.org/ packages/ wahay-bin/

Are you accepting PRs to the README#Install, or can you update the website with a link to the install?

As far as I can tell, all users who are connected to a meeting access it via the onion service. If that's accurate, it seems wasteful to make the user who's hosting the meeting do so, since they don't need to stay anonymous from themselves. Making the user who's hosting a meeting connect via localhost instead of the onion service would cut the latency in half for 2-party calls, and would improve the latency for the portions of conference calls where the host is a participant as well. Is there any security rationale for not doing so that I'm overlooking?

Its better to have sandboxing profile like apparmor or using namespaces through firejail (can have both), If one to be chosen then for surely apparmor profile.

Hi! I love the idea of the project. I saw that the support for macOS is comming soon, and I wondered whether I could help porting it to the platform.

I am new to the project, will need some time to get familiar with the architecture and so on, but could any of you point me to some key things that need to be done in order to port it to macOS?

Hi!

We've talked in the past about adding Wahay to Tails. One of the prerequesites is to have it in Debian.

There have been a few experiment done on both front (Tails issue tracker is a good starting point).

So, in order to determine if we indeed want to invest ressources on it now, I'd like to know what the status of this project is?

How do you see the future (say, mid-term / long term)?

Thanks! :)

I2P has many benefits over Tor for e.g:

• P2P (Tor is not p2p).
• Support UDP and TCP (Tor only TCP) , This is beneficially specially for VOIP.
• Support IPv4 and IPv6 (Tor lately started to support some of IPv6, But mainly its IPv4).

I dont say to deprecate Tor , But having both wont harm and useful as well to use different paths of secure communications.