Discussion:
paganini (y)
(too old to reply)
Sentinelle Aveugle Kdog
2024-11-08 19:38:41 UTC
Permalink
This is paganini test
OK?
Stefan Claas
2024-11-08 19:40:55 UTC
Permalink
Sentinelle Aveugle Kdog wrote:
>
> This is paganini test
> OK?

yes.

Regards
Stefan
kosmikdog
2024-11-08 21:13:42 UTC
Permalink
Stefan Claas wrote:

> yes.

On the other hand oc_guard_server gives me this error:

> ***@chezmoi:~/oc/oc_guard_server$ package oc_guard_server is not in std (/usr/lib/go/src/oc_guard_server)
> ^C
> [3]+ Exit 1 go run oc_guard_server -s /home/kdog/minicrypt/private.pem

I'm on arch.
Regards

KD
Stefan Claas
2024-11-08 22:03:05 UTC
Permalink
kosmikdog wrote:
> Stefan Claas wrote:
>
> > yes.
>
> On the other hand oc_guard_server gives me this error:
>
> > ***@chezmoi:~/oc/oc_guard_server$ package oc_guard_server is not in std (/usr/lib/go/src/oc_guard_server)
> > ^C
> > [3]+ Exit 1 go run oc_guard_server -s /home/kdog/minicrypt/private.pem

Please compile it with go mod init and go mod tidy and then run the binary.

Regards
Stefan
Stefan Claas
2024-11-09 19:52:09 UTC
Permalink
Stefan Claas wrote:
> kosmikdog wrote:
> > Stefan Claas wrote:
> >
> > > yes.
> >
> > On the other hand oc_guard_server gives me this error:
> >
> > > ***@chezmoi:~/oc/oc_guard_server$ package oc_guard_server is not in std (/usr/lib/go/src/oc_guard_server)
> > > ^C
> > > [3]+ Exit 1 go run oc_guard_server -s /home/kdog/minicrypt/private.pem
>
> Please compile it with go mod init and go mod tidy and then run the binary.

I just saw that you forgot the .go extension...

--
Regards
Stefan
kosmikdog
2024-11-10 09:57:37 UTC
Permalink
Stefan Claas wrote:
>
> I just saw that you forgot the .go extension...
>

you are right, pardon!

> ~/oc/oc_client$ go run oc_client.go -f file.txt -clearnet 127.0.0.1:8084 0FAsB4R15iz7
> Using clearnet
> Send file...
>
> Error uploading file: unexpected status: 500 Internal Server Error, body: Error decrypting content: error decrypting: illegal base64 data at input byte 1
>
> exit status 1

Regards
Onion Courier
2024-11-10 16:51:16 UTC
Permalink
kosmikdog wrote:
> Stefan Claas wrote:
> >
> > I just saw that you forgot the .go extension...
> >
>
> you are right, pardon!
>
> > ~/oc/oc_client$ go run oc_client.go -f file.txt -clearnet 127.0.0.1:8084 0FAsB4R15iz7
> > Using clearnet
> > Send file...
> >
> > Error uploading file: unexpected status: 500 Internal Server Error, body: Error decrypting content: error decrypting: illegal base64 data at input byte 1
> >
> > exit status 1

You need to encrypt the message first with minicrypt and the Guard's public key.

--
Regards
Stefan
kosmikdog
2024-11-10 22:37:59 UTC
Permalink
Onion Courier wrote:
>
> You need to encrypt the message first with minicrypt and the Guard's public key.
>

Facing this error with tor socks:

https://privatebin.virebent.art/?6ea75b82361be9fe#FERQ14Abzsi6XEqm5QeV1zhK8YMwoA8HmgegxbYAAE4X
Stefan Claas
2024-11-11 11:00:43 UTC
Permalink
kosmikdog wrote:
> Onion Courier wrote:
> >
> > You need to encrypt the message first with minicrypt and the Guard's public key.
> >
>
> Facing this error with tor socks:
>
> https://privatebin.virebent.art/?6ea75b82361be9fe#FERQ14Abzsi6XEqm5QeV1zhK8YMwoA8HmgegxbYAAE4X

Are both servers running? You also did not tell, after encryption, if you succeded
with your previous posting.

--
Regards
Stefan
kosmikdog
2024-11-11 17:25:15 UTC
Permalink
Stefan Claas wrote:
> Are both servers running? You also did not tell, after encryption, if you succeded
> with your previous posting.
>

Hi Stef,
yes, they are listening

> tcp6 0 0 :::8081 :::* LISTEN 153850/oc_m2n_serve
> tcp6 0 0 :::8082 :::* LISTEN 14506/oc_paganini_s
> tcp6 0 0 :::8084 :::* LISTEN 144594/oc_guard_ser

Proceeding for attempts, I encrypted with minicrypt the body of the
message arbitrarily by putting the headers of the mail in a separate
file, the data.txt, from: to: newsgroups: etc.!;
It didn't work.
In another email I encrypted the entire message with headers and however
always shows an error of socks 9050 of tor, which has nothing to do with
the validity of the message format.
And the error is always that shown on the pastebin for port m2n 8081 e
guard 8084.

Regards
kosmikdog
2024-11-11 17:32:29 UTC
Permalink
kosmikdog wrote:

> Regards

Yes i have created a key pair for the oc_guard_server and it's been
launched '-s private.pem' .

Regards
Stefan Claas
2024-11-11 18:07:19 UTC
Permalink
kosmikdog wrote:
> kosmikdog wrote:
>
> > Regards
>
> Yes i have created a key pair for the oc_guard_server and it's been
> launched '-s private.pem' .
>
> Regards

Ok, now let's see what happens if you follow my previous reply.

--
Regards
Stefan
Stefan Claas
2024-11-11 18:05:55 UTC
Permalink
kosmikdog wrote:
> Stefan Claas wrote:
> > Are both servers running? You also did not tell, after encryption, if you succeded
> > with your previous posting.
> >
>
> Hi Stef,
> yes, they are listening
>
> > tcp6 0 0 :::8081 :::*
> > LISTEN 153850/oc_m2n_serve tcp6 0 0 :::8082
> >
> >
> >
> > :::* LISTEN 14506/oc_paganini_s tcp6 0
> >
> > 0 :::8084 :::* LISTEN
> > 144594/oc_guard_ser
>
> Proceeding for attempts, I encrypted with minicrypt the body of the
> message arbitrarily by putting the headers of the mail in a separate
> file, the data.txt, from: to: newsgroups: etc.!;
> It didn't work.
> In another email I encrypted the entire message with headers and however
> always shows an error of socks 9050 of tor, which has nothing to do with
> the validity of the message format.
> And the error is always that shown on the pastebin for port m2n 8081 e
> guard 8084.

Weel, I don't know why you get the error, maybe because you use 127.0.0.1:port,
pw instead of the onionURl:port pw.

Try the following again please, write a test message with the X-OC-To: Header
in your test message, which has your m2n onionURL:port pw as X-OC-To Header,
followed by all other Usenet Headers. Encrypt with minicrypt and send this
encrypted message, without any Headers, to your Guard server, but do not use
127.0.0.1:port pw and use instead your Guard's onionURL:port pw. This should
always work, assuming your servers are running, ports are open and can be reached
for example with Tor Browser.

--
Regards
Stefan
kosmikdog
2024-11-11 20:53:18 UTC
Permalink
Stefan Claas wrote:

> Weel, I don't know why you get the error, maybe because you use 127.0.0.1:port,
> pw instead of the onionURl:port pw.

This because i missed to use -clearnet option vs host 127.0.0.1:8084 passwd.

> Try the following again please, write a test message with the X-OC-To: Header
> in your test message, which has your m2n onionURL:port pw as X-OC-To Header,

Oc_m2n worked!

> followed by all other Usenet Headers. Encrypt with minicrypt and send this
> encrypted message, without any Headers, to your Guard server, but do not use
> 127.0.0.1:port pw and use instead your Guard's onionURL:port pw. This should
> always work, assuming your servers are running, ports are open and can be reached
> for example with Tor Browser.
>

I have pasted the message in clear to show you the format i used for the
actual message, followed by oc_guard_server debug messages.

https://privatebin.virebent.art/?c1a1bea109619abc#8uTQmTHt6NtHG32ufuzap8wbHhvK6SPaMsbdaCHauQrr

I have encrypted my message by the public key i created for oc_guard.
It should decrypt body and headers by the private key is running with.
But it doesnt get through.
The tor version i run with it's 0.4.8.12 and it has default
configuration but the oc_server hidden addresses.

regards
Stefan Claas
2024-11-12 12:54:11 UTC
Permalink
kosmikdog wrote:
> Stefan Claas wrote:
>
> > Weel, I don't know why you get the error, maybe because you use 127.0.0.1:port,
> > pw instead of the onionURl:port pw.
>
> This because i missed to use -clearnet option vs host 127.0.0.1:8084 passwd.
>
> > Try the following again please, write a test message with the X-OC-To: Header
> > in your test message, which has your m2n onionURL:port pw as X-OC-To Header,
>
> Oc_m2n worked!
>
> > followed by all other Usenet Headers. Encrypt with minicrypt and send this
> > encrypted message, without any Headers, to your Guard server, but do not use
> > 127.0.0.1:port pw and use instead your Guard's onionURL:port pw. This should
> > always work, assuming your servers are running, ports are open and can be reached
> > for example with Tor Browser.
> >
>
> I have pasted the message in clear to show you the format i used for the
> actual message, followed by oc_guard_server debug messages.
>
> https://privatebin.virebent.art/?c1a1bea109619abc#8uTQmTHt6NtHG32ufuzap8wbHhvK6SPaMsbdaCHauQrr
>
> I have encrypted my message by the public key i created for oc_guard.
> It should decrypt body and headers by the private key is running with.
> But it doesnt get through.
> The tor version i run with it's 0.4.8.12 and it has default
> configuration but the oc_server hidden addresses.

Please use my Guard node for a test, or give me from yours the data,
so that I can test your Guard node.

--
Regards
Stefan
Sentinelle Aveugle Kdog
2024-11-11 18:51:50 UTC
Permalink
This what happens launching oc_client vs oc_guard

/oc/oc_client$ go run oc_client.go -f file.crypt 127.0.0.1:8084 0FAsB4R15iz7
Using Tor network
Send file...

Error uploading file: failed to send request: Post "http://127.0.0.1:8084/upload": socks connect tcp localhost:9050->127.0.0.1:8084: unknown error general SOCKS server failure
exit status 1

This is a test
Regards
Stefan Claas
2024-11-11 19:49:41 UTC
Permalink
Sentinelle Aveugle Kdog wrote:
>
> This what happens launching oc_client vs oc_guard
>
> /oc/oc_client$ go run oc_client.go -f file.crypt 127.0.0.1:8084 0FAsB4R15iz7
> Using Tor network
> Send file...
>
> Error uploading file: failed to send request: Post "http://127.0.0.1:8084/upload": socks connect tcp localhost:9050->127.0.0.1:8084: unknown error general SOCKS server failure
> exit status 1
>
> This is a test
> Regards
>

Did you read my previous posting and understood what I said?

Sorry to say that, but I can not give indefinetly support for
such things. The project just works fine as it is, when properly
used. I may consider to update the READMEs to reflect that better,
after seeing that you produce with your set-up so many erros, which
really should not happen, seriously!

I suggest that you first try to use oc_client_go and oc_server.go,
with sending messages to your inbox *via an onionURL* and not 127.0.0.1,
so that you see things work, while traveling over the Tor Network.

Then you may use a middleman with an X-OC-To: Header and so on, and
always use onionURLs and not 127.0.0.1.

Or check out your settings again for your posting to it.test, which
worked.

Sorry that I can not help you better! I made things as easy as possible
for users!

I tested all software components also locally and not only via VPS and
it works 100%.

--
Regards
Stefan
Nomen Nescio
2024-11-09 02:05:01 UTC
Permalink
On Fri, 8 Nov 2024 19:38:41 -0000 (UTC), you wrote:
>
> This is paganini test
> OK?

What are the settings to use this paganini news provider?
Loading...