[Replicant] error while sending image with Conversations through Orbot

Adonay Felipe Nogueira adfeno at hyperbola.info
Tue May 10 23:52:11 UTC 2022


Sorry for late reply, I don't use Orbot currently, but I think that the cause of the error sending stuff through it is related to the warning it gives related to “rejecting SOCKS request for anonymous connection to private address”.

Em 13 de dezembro de 2021 20:36:35 BRT, Fil Lupin via Replicant <replicant at osuosl.org> escreveu:
>Hi,
>
>trying to change the rights and owner of /storage content does not work.
>
>I got some log when bug occurs : when sending a picture through tor (orbot 16.4.1-RC-2-tor.0.4.4.6 / Tor 0.4.4.6-openssl1.1.1g) on android 4.2.2 and conversations 2.9.3+fcr, I got the following error: failure to connect to socks server.
>
>Here is the logcat output:
>
>--------- beginning of /dev/log/main
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 443 is already being handled; removing.
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 5222 is already being handled; removing.
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 443 is already being handled; removing.
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 5222 is already being handled; removing.
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 443 is already being handled; removing.
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 5222 is already being handled; removing.
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 443 is already being handled; removing.
>D/Orbot   ( 2959): DEBUG: circuit_remove_handled_ports: Port 5222 is already being handled; removing.
>D/conversations( 2665): send file message
>D/conversations( 2665): using 12-byte IV for file transmission
>D/Orbot   ( 2959): DEBUG: conn_read_callback: socket 18 wants to read.
>D/Orbot   ( 2959): DEBUG: read_to_chunk: Read 242 bytes. 242 on inbuf.
>D/Orbot   ( 2959): DEBUG: circuit_consider_stop_edge_reading: considering layer_hint->package_window 969
>D/Orbot   ( 2959): DEBUG: circuit_consider_stop_edge_reading: considering layer_hint->package_window 969
>D/Orbot   ( 2959): DEBUG: connection_edge_package_raw_inbuf: 18: Packaging 242 bytes (0 waiting).
>D/Orbot   ( 2959): DEBUG: relay_send_command_from_edge_: delivering 2 cell forward.
>D/Orbot   ( 2959): DEBUG: relay_encrypt_cell_outbound: encrypting a layer of the relay cell.
>D/Orbot   ( 2959): DEBUG: relay_encrypt_cell_outbound: encrypting a layer of the relay cell.
>D/Orbot   ( 2959): DEBUG: relay_encrypt_cell_outbound: encrypting a layer of the relay cell.
>D/Orbot   ( 2959): DEBUG: append_cell_to_circuit_queue: Made a circuit active.
>D/Orbot   ( 2959): DEBUG: scheduler_set_channel_state: chan 5 changed from scheduler state WAITING_FOR_CELLS to PENDING
>D/Orbot   ( 2959): DEBUG: sendme_note_circuit_data_packaged: Circuit package_window now 968.
>D/Orbot   ( 2959): DEBUG: sendme_note_stream_data_packaged: Stream package_window now 468.
>D/Orbot   ( 2959): DEBUG: connection_edge_package_raw_inbuf: conn->package_window is now 468
>D/Orbot   ( 2959): DEBUG: circuit_consider_stop_edge_reading: considering layer_hint->package_window 968
>D/Orbot   ( 2959): DEBUG: scheduler_evt_callback: Scheduler event callback called
>D/Orbot   ( 2959): DEBUG: update_socket_info: chan=5 updated socket info, limit: 15456, cwnd: 6, unacked: 0, notsent: 0, mss: 1288
>D/Orbot   ( 2959): DEBUG: kist_scheduler_run: Running the scheduler. 1 channels pending
>D/Orbot   ( 2959): DEBUG: outbuf_table_add: scheduler init outbuf info for chan=5
>D/Orbot   ( 2959): DEBUG: channel_write_packed_cell: Writing 0x2b310208 to channel 0x2b2e5d50 with global ID 5
>D/Orbot   ( 2959): DEBUG: channel_flush_from_first_active_circuit: Made a circuit inactive.
>D/Orbot   ( 2959): DEBUG: update_socket_written: chan=5 wrote 543 bytes, old was 0
>D/Orbot   ( 2959): DEBUG: scheduler_set_channel_state: chan 5 changed from scheduler state PENDING to WAITING_FOR_CELLS
>D/Orbot   ( 2959): DEBUG: channel_write_to_kernel: Writing 514 bytes to kernel for chan 5
>D/Orbot   ( 2959): DEBUG: flush_chunk_tls: flushed 514 bytes, 0 ready to flush, 0 remain.
>D/Orbot   ( 2959): DEBUG: connection_handle_write_impl: After TLS write of 514: 0 read, 536 written
>D/Orbot   ( 2959): DEBUG: free_outbuf_info_by_ent: Freeing outbuf table entry from chan=5
>D/Orbot   ( 2959): DEBUG: kist_scheduler_run: len pending=0, len to_readd=-1
>I/Choreographer( 2665): Skipped 35 frames!  The application may be doing too much work on its main thread.
>D/Orbot   ( 2959): DEBUG: conn_read_callback: socket 16 wants to read.
>D/Orbot   ( 2959): DEBUG: connection_buf_read_from_socket: 16: starting, inbuf_datalen 0 (0 pending in tls object). at_most 16448.
>D/Orbot   ( 2959): DEBUG: connection_buf_read_from_socket: After TLS read of 1028: 1050 read, 0 written
>D/Orbot   ( 2959): DEBUG: connection_or_process_cells_from_inbuf: 16: starting, inbuf_datalen 1028 (0 pending in tls object).
>D/Orbot   ( 2959): DEBUG: channel_process_cell: Processing incoming cell_t 0xbefff168 for channel 0x2b2e5d50 (global ID 5)
>D/Orbot   ( 2959): DEBUG: circuit_get_by_circid_channel_impl: circuit_get_by_circid_channel_impl() returning circuit 0x2b05bd78 for circ_id 4070183511, channel ID 5 (0x2b2e5d50)
>D/Orbot   ( 2959): DEBUG: relay_lookup_conn: found conn for stream 313.
>D/Orbot   ( 2959): DEBUG: circuit_receive_relay_cell: Sending to origin.
>D/Orbot   ( 2959): DEBUG: connection_edge_process_relay_cell: Now seen 2995 relay cells here (command 2, stream 313).
>D/Orbot   ( 2959): DEBUG: sendme_circuit_data_received: Circuit deliver_window now 933.
>D/Orbot   ( 2959): DEBUG: connection_or_process_cells_from_inbuf: 16: starting, inbuf_datalen 514 (0 pending in tls object).
>D/Orbot   ( 2959): DEBUG: channel_process_cell: Processing incoming cell_t 0xbefff168 for channel 0x2b2e5d50 (global ID 5)
>D/Orbot   ( 2959): DEBUG: circuit_get_by_circid_channel_impl: circuit_get_by_circid_channel_impl() returning circuit 0x2b05bd78 for circ_id 4070183511, channel ID 5 (0x2b2e5d50)
>D/Orbot   ( 2959): DEBUG: relay_lookup_conn: found conn for stream 313.
>D/Orbot   ( 2959): DEBUG: circuit_receive_relay_cell: Sending to origin.
>D/Orbot   ( 2959): DEBUG: connection_edge_process_relay_cell: Now seen 2996 relay cells here (command 2, stream 313).
>D/Orbot   ( 2959): DEBUG: sendme_circuit_data_received: Circuit deliver_window now 932.
>D/Orbot   ( 2959): DEBUG: connection_or_process_cells_from_inbuf: 16: starting, inbuf_datalen 0 (0 pending in tls object).
>D/conversations( 2665): uploading to https://WEBSITE.org/upload/cfee2913ce572d9ebb0a968a72b035ab87396582/E4xfTeGg2FgR1zwfvorI/JzHGAlfnQuyaAw6yeWM22w.jpg w/ read timeout of 56s
>D/Orbot   ( 2959): DEBUG: conn_write_callback: socket 18 wants to write.
>D/Orbot   ( 2959): DEBUG: conn_read_callback: socket 18 wants to read.
>D/Orbot   ( 2959): DEBUG: read_to_chunk: Read 56 bytes. 56 on inbuf.
>D/Orbot   ( 2959): DEBUG: circuit_consider_stop_edge_reading: considering layer_hint->package_window 968
>D/Orbot   ( 2959): DEBUG: circuit_consider_stop_edge_reading: considering layer_hint->package_window 968
>D/Orbot   ( 2959): DEBUG: connection_edge_package_raw_inbuf: 18: Packaging 56 bytes (0 waiting).
>D/Orbot   ( 2959): DEBUG: relay_send_command_from_edge_: delivering 2 cell forward.
>D/Orbot   ( 2959): DEBUG: relay_encrypt_cell_outbound: encrypting a layer of the relay cell.
>D/Orbot   ( 2959): DEBUG: relay_encrypt_cell_outbound: encrypting a layer of the relay cell.
>D/Orbot   ( 2959): DEBUG: relay_encrypt_cell_outbound: encrypting a layer of the relay cell.
>D/Orbot   ( 2959): DEBUG: append_cell_to_circuit_queue: Made a circuit active.
>D/Orbot   ( 2959): DEBUG: scheduler_set_channel_state: chan 5 changed from scheduler state WAITING_FOR_CELLS to PENDING
>D/Orbot   ( 2959): DEBUG: sendme_note_circuit_data_packaged: Circuit package_window now 967.
>D/Orbot   ( 2959): DEBUG: sendme_note_stream_data_packaged: Stream package_window now 467.
>D/Orbot   ( 2959): DEBUG: connection_edge_package_raw_inbuf: conn->package_window is now 467
>D/Orbot   ( 2959): DEBUG: circuit_consider_stop_edge_reading: considering layer_hint->package_window 967
>D/Orbot   ( 2959): DEBUG: scheduler_evt_callback: Scheduler event callback called
>D/Orbot   ( 2959): DEBUG: update_socket_info: chan=5 updated socket info, limit: 15456, cwnd: 6, unacked: 0, notsent: 0, mss: 1288
>D/Orbot   ( 2959): DEBUG: kist_scheduler_run: Running the scheduler. 1 channels pending
>D/Orbot   ( 2959): DEBUG: outbuf_table_add: scheduler init outbuf info for chan=5
>D/Orbot   ( 2959): DEBUG: channel_write_packed_cell: Writing 0x2b310208 to channel 0x2b2e5d50 with global ID 5
>D/Orbot   ( 2959): DEBUG: channel_flush_from_first_active_circuit: Made a circuit inactive.
>D/Orbot   ( 2959): DEBUG: update_socket_written: chan=5 wrote 543 bytes, old was 0
>D/Orbot   ( 2959): DEBUG: scheduler_set_channel_state: chan 5 changed from scheduler state PENDING to WAITING_FOR_CELLS
>D/Orbot   ( 2959): DEBUG: channel_write_to_kernel: Writing 514 bytes to kernel for chan 5
>D/Orbot   ( 2959): DEBUG: flush_chunk_tls: flushed 514 bytes, 0 ready to flush, 0 remain.
>D/Orbot   ( 2959): DEBUG: connection_handle_write_impl: After TLS write of 514: 0 read, 536 written
>D/Orbot   ( 2959): DEBUG: free_outbuf_info_by_ent: Freeing outbuf table entry from chan=5
>D/Orbot   ( 2959): DEBUG: kist_scheduler_run: len pending=0, len to_readd=-1
>D/Orbot   ( 2959): DEBUG: conn_read_callback: socket 7 wants to read.
>D/Orbot   ( 2959): DEBUG: connection_handle_listener_read: Connection accepted on socket 15 (child of fd 7).
>D/Orbot   ( 2959): INFO: connection_handle_listener_read: New SOCKS connection opened from 127.0.0.1.
>D/Orbot   ( 2959): DEBUG: connection_add_impl: new conn type Socks, socket 15, address 127.0.0.1, n_conns 10.
>D/Orbot   ( 2959): DEBUG: conn_read_callback: socket 15 wants to read.
>D/Orbot   ( 2959): DEBUG: read_to_chunk: Read 16 bytes. 16 on inbuf.
>D/Orbot   ( 2959): DEBUG: connection_ap_handshake_process_socks: entered.
>D/Orbot   ( 2959): StreamStatus (50): NEW
>W/System.err( 2665): java.io.IOException: Failure to connect to SOCKS server
>D/Orbot   ( 2959): DEBUG: connection_ap_handshake_rewrite: Client asked for 127.0.0.1:9050
>D/Orbot   ( 2959): WARN: Rejecting SOCKS request for anonymous connection to private address 127.0.0.1. [1 similar message(s) suppressed in last 300 seconds]
>D/Orbot   ( 2959): StreamStatus (50): FAILED
>D/Orbot   ( 2959): DEBUG: conn_close_if_marked: Cleaning up connection (fd 15).
>D/Orbot   ( 2959): StreamStatus (50): CLOSED
>D/Orbot   ( 2959): DEBUG: connection_remove: removing socket 15 (type Socks), n_conns now 10
>D/Orbot   ( 2959): DEBUG: connection_free_minimal: closing fd 15.
>D/Orbot   ( 2959): DEBUG: conn_read_callback: socket 7 wants to read.
>D/Orbot   ( 2959): DEBUG: connection_handle_listener_read: Connection accepted on socket 15 (child of fd 7).
>D/Orbot   ( 2959): INFO: connection_handle_listener_read: New SOCKS connection opened from 127.0.0.1.
>D/Orbot   ( 2959): DEBUG: connection_add_impl: new conn type Socks, socket 15, address 127.0.0.1, n_conns 10.
>D/Orbot   ( 2959): DEBUG: conn_read_callback: socket 15 wants to read.
>D/Orbot   ( 2959): DEBUG: read_to_chunk: Read 16 bytes. 16 on inbuf.
>D/Orbot   ( 2959): DEBUG: connection_ap_handshake_process_socks: entered.
>D/Orbot   ( 2959): StreamStatus (51): NEW
>D/Orbot   ( 2959): DEBUG: connection_ap_handshake_rewrite: Client asked for 127.0.0.1:9050
>D/Orbot   ( 2959): StreamStatus (51): FAILED
>D/Orbot   ( 2959): DEBUG: conn_close_if_marked: Cleaning up connection (fd 15).
>D/Orbot   ( 2959): StreamStatus (51): CLOSED
>D/Orbot   ( 2959): DEBUG: connection_remove: removing socket 15 (type Socks), n_conns now 10
>D/Orbot   ( 2959): DEBUG: connection_free_minimal: closing fd 15.
>W/System.err( 2665): 	at java.net.PlainSocketImpl.socksRequestConnection(PlainSocketImpl.java:345)
>W/System.err( 2665): 	at java.net.PlainSocketImpl.socksConnect(PlainSocketImpl.java:329)
>W/System.err( 2665): 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:190)
>W/System.err( 2665): 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:459)
>W/System.err( 2665): 	at java.net.Socket.connect(Socket.java:842)
>W/System.err( 2665): 	at libcore.net.http.HttpConnection.<init>(HttpConnection.java:76)
>W/System.err( 2665): 	at libcore.net.http.HttpConnection.<init>(HttpConnection.java:50)
>W/System.err( 2665): 	at libcore.net.http.HttpConnection$Address.connect(HttpConnection.java:340)
>W/System.err( 2665): 	at libcore.net.http.HttpConnectionPool.get(HttpConnectionPool.java:87)
>W/System.err( 2665): 	at libcore.net.http.HttpConnection.connect(HttpConnection.java:98)
>W/System.err( 2665): 	at libcore.net.http.HttpEngine.openSocketConnection(HttpEngine.java:316)
>W/System.err( 2665): 	at libcore.net.http.HttpsURLConnectionImpl$HttpsEngine.makeSslConnection(HttpsURLConnectionImpl.java:461)
>W/System.err( 2665): 	at libcore.net.http.HttpsURLConnectionImpl$HttpsEngine.connect(HttpsURLConnectionImpl.java:442)
>W/System.err( 2665): 	at libcore.net.http.HttpEngine.sendSocketRequest(HttpEngine.java:290)
>W/System.err( 2665): 	at libcore.net.http.HttpEngine.sendRequest(HttpEngine.java:240)
>W/System.err( 2665): 	at libcore.net.http.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:81)
>W/System.err( 2665): 	at libcore.net.http.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:165)
>W/System.err( 2665): 	at eu.siacs.conversations.http.HttpUploadConnection.upload(HttpUploadConnection.java:187)
>W/System.err( 2665): 	at eu.siacs.conversations.http.HttpUploadConnection.access$300(HttpUploadConnection.java:30)
>W/System.err( 2665): 	at eu.siacs.conversations.http.HttpUploadConnection$1.lambda$success$0(HttpUploadConnection.java:139)
>W/System.err( 2665): 	at eu.siacs.conversations.http.-$$Lambda$HttpUploadConnection$1$ektaHXFqxgW3UQRYD5-n6pWZA0w.run(lambda)
>W/System.err( 2665): 	at java.lang.Thread.run(Thread.java:856)
>D/conversations( 2665): http upload failed Failure to connect to SOCKS server
>
>Do you know have any idea of how I could solve this?
>
>Regards,
>
>
>- Fil Lupin.
>
>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>On Friday, November 12, 2021 9:49 AM, Fil Lupin <fillupin at protonmail.com> wrote:
>
>> Hello,
>> I noticed the directory rights are not set identically for each /storage directory:
>>
>> root at android:/storage # ll
>> dr-xr-xr-x root root 2021-11-04 10:50 emulated
>> lrwxrwxrwx root root 2021-11-04 10:50 sdcard0 -> /storage/emulated/legacy
>> d---rwxr-x system sdcard_rw 1970-01-01 01:00 sdcard1
>> drwxrwxr-x system system 2021-11-04 10:50 usbdisk0
>>
>> Since emulated and usbdisk0 seems not well configurated, I could try to change owner or change directory rights, but I would prefer to change it the way it should be.
>>
>> Could you tell me what is the normal configuration of each /storage directory (ideally in replicant 4.2/samsung GT-I9300, at least replicant 6/samsung GT-I9300).
>>
>> Regards,
>>
>> -   Fil Lupin.
>>
>>     ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>
>>     On Thursday, October 28th, 2021 at 8:56 AM, Fil Lupin via Replicant replicant at osuosl.org wrote:
>>
>>
>> > Hi,
>> > did my answers allows anyone to understand better the issue I have on my Galaxy S3 by chance?
>> > I have to say I don't see any direction to follow for now...
>> >
>> > -   Fil Lupin.
>> >     ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> >     On Wednesday, October 20th, 2021 at 11:38 PM, Fil Lupin via Replicant replicant at osuosl.org wrote:
>> >
>> >
>> > > Hi Denis,
>> > > thank you for your answer.
>> > > My answers follows...
>> > > On Friday, October 15th, 2021 at 2:02 PM, Denis 'GNUtoo' Carikli GNUtoo at cyberdimension.org wrote:
>> > >
>> > > > On Tue, 05 Oct 2021 18:12:10 +0000
>> > > > Fil Lupin via Replicant replicant at osuosl.org wrote:
>> > > >
>> > > > > Hi again,
>> > > > > I checked and I do not receive MMS neither.
>> > > > > However, there is no problem known in my country receiving MMS, nor
>> > > > > with my operator for receiving MMS. My understanding is this is due
>> > > > > to my phone.
>> > > >
>> > > > I don't remember well Replicant 4.2, but assuming it's like Replicant
>> > > > 6.0, if you open the File Manager application, and that you click on
>> > > > the icon with 3 horizontal lines, do you see the internal storage? And
>> > > > can you access it and read or write files in it?
>> > >
>> > > I can create files in /storage/sdcard0 and /storage/sdcard1 but not in /storage/emulated and /storage/usbdisk0
>> > >
>> > > > If that works, do the applications sending / receiving MMS or can
>> > > > Conversations access that storage as well? In Replicant 6,
>> > > > you can set or verify that in Settings->Apps->[The
>> > > > application]->Permissions.
>> > >
>> > > They can modify or delete content of sd card.
>> > >
>> > > -   Fil Lupin.
>
>_______________________________________________
>Replicant mailing list
>Replicant at osuosl.org
>https://lists.osuosl.org/mailman/listinfo/replicant

-- 
* https://libreplanet.org/wiki/User:Adfeno
* Ativista não advogado, nem técnico de informática
* Compre dos vendedores locais
* Use e contribua ao software livre (diferente do gratuito)
* Enviando docs.? Use OpenDocument. Outros tipos: vide endereço anterior
* Use XMPP (federado, pai do WhatsApp)
* E-mails assinados com OpenPGP (anexo "signature.asc")
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/replicant/attachments/20220510/c9579537/attachment-0001.asc>


More information about the Replicant mailing list