iyouport-org/relaybaton

A pluggable transport to circumvent Internet censorship

relaybaton's Issues

No longer works on cloud flare ?

I read that clodflare no longer allows both ESNI and SNI connections.

Can you let me know ?

I can build this into flutter and so build mobile and desktop apps using it.

no exported names

1. trying to build with Mac with make mobile.. i got this error

no exported names in the package "dir/relaybaton_master/cmd/relaybaton_mobile"

2. make desktop has this error too
   pkg/core/server_web.go:103:5: duplicate field name in struct literal: PlanID
   make: *** [desktop] Error 2

Errors found

github.com/iyouport-org/relaybaton/pkg/core

/Users/mcbook/Desktop/relaybaton-master/pkg/core/conn.go:64:4: unknown field 'ClientESNIKeys' in struct literal of type tls.Config
/Users/mcbook/Desktop/relaybaton-master/pkg/core/conn.go:199:31: undefined: tls.ESNIKeys
/Users/mcbook/Desktop/relaybaton-master/pkg/core/conn.go:211:18: undefined: tls.ParseESNIKeys
/Users/mcbook/Desktop/relaybaton-master/pkg/core/server_web.go:103:5: duplicate field name in struct literal: PlanID
rm -r -f "$WORK"
gomobile: go build -v -x -ldflags -w -buildmode=c-shared -
o=/var/folders/p3/s_s0szld2k90_vkbkxqm5vjc0000gn/T/gomobile-work-090470570/android/src/main/jniLibs/armeabi-v7a/libgojni.so ./gobind failed: exit status 2

Error 1 Compiling

Please am not an expert, but i tried compiling the ECH branch and i get this error

github.com/iyouport-org/relaybaton/cmd/cli imports
github.com/spf13/viper imports
github.com/spf13/afero imports
io/fs: package io/fs is not in GOROOT (/usr/local/go/src/io/fs)
Makefile:63: recipe for target '/root/relaybaton-ech/vendor' failed
make: *** [/root/relaybaton-ech/vendor] Error 1

Please what am i doing wrong.

thanks

ERROR says it all in the photos!

draft: relaybaton URI specification

Scheme

relaybaton://user:pass@host[#remarks]

Basic

relaybaton URIs should be standard URIs, not something using JSON and Base64 encoding, etc.

Rules

• username and password must be in accordance with specifications encode, not directly collage
• remarks must be in full-encoded URL encode format, instead of allowing spaces or direct collage