333.i2p

Предлагаю обновить ссылку на флибусту
http://xcktsvspaz4iu24g65vuzuvoagqzfilqaa6h5btg...

Нашёл тут
http://r4sas.i2p/index.php?entry=%C7%E5%F0%EA%E...

Привет.

Предлагаю свою недо радио станция : http://kasy-radio.i2p/
1. Язык руский
2. Аптайм субота васкрисения 24/2

Баннер: http://kasy-radio.i2p/baner.png

п.с нету смисла моево проекта лол ;)

librarian.i2p

сайт хороший, я не создатель, но если добавите, баннер нарисую!

zpkg & junest

I've been on a bad streak lately. Everything I tried did not work. I've spent 2 hours on zpkg and 2 hours on junest. None of them worked for me. I tried some other things like gentoo for Debian (sudo apt install gentoo). Nothing worked.

Has anybody got something i2p related with zpkg or junest?

https://ihucos.github.io/zpkg/
https://github.com/fsquillace/junest

Qball wrote:

user@disp9934 ~ $ sudo du -shx ~i2pd/[pn][e]*
du: cannot access '/var/lib/i2pd/[pn][e]*': No such file or directory

I gave up on Ubuntu and i2pd 2.48. There are to many problems with both. This is from a very good router:
user@disp9934 ~ $ top -b | head
top - 08:46:24 up 1:02, 1 user, load average: 1.74, 1.32, 1.17
Tasks: 181 total, 2 running, 179 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.0 sy, 50.0 ni, 43.8 id, 0.0 wa, 3.1 hi, 0.0 si, 3.1 st
MiB Mem : 2534.0 total, 643.1 free, 839.2 used, 1051.7 buff/cache
MiB Swap: 1024.0 total, 1023.2 free, 0.8 used. 1490.1 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
989 user 39 19 730232 114436 16640 R 100.0 4.4 54:10.58 tracker+
1 root 20 0 98476 11008 8448 S 0.0 0.4 0:00.13 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
user@disp9934 ~ $ sudo du -shx ~i2pd/[pn][e]*
du: cannot access '/var/lib/i2pd/[pn][e]*': No such file or directory
user@disp9934 ~ $

This should be probably in a new topic.
Is there a torrent client for yggdrasil? Maybe a modified aria2?
I also have some i2pd routers that collapse on Yggdrasil but the same setup works through Tor.

Qball wrote:

amnesia@amnesia:~$ sudo -shx ~i2pd/[pn][e]*

17M /var/lib/i2pd/netDb
18M /var/lib/i2pd/peerProfiles

If they are too big - you may remove this two folder preventive.

Both snapstore and github downloads are not available anymore. It appears that the flatpak too suffers from the problem.

amnesia@amnesia:~$ top -b | head
top - 15:56:38 up 9:23, 1 user, load average: 0.16, 0.34, 0.16
Tasks: 224 total, 1 running, 222 sleeping, 0 stopped, 1 zombie
%Cpu(s): 0.0 us, 3.0 sy, 3.0 ni, 93.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 3779.7 total, 273.7 free, 1980.9 used, 1525.0 buff/cache
MiB Swap: 7875.5 total, 7567.0 free, 308.5 used. 1407.2 avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1827 amnesia 26 6 173280 7552 6784 S 6.2 0.2 0:00.15 ibus-en+
6483 amnesia 26 6 22912 4096 3328 R 6.2 0.1 0:00.01 top
1 root 20 0 166712 11348 7892 S 0.0 0.3 0:01.62 systemd
amnesia@amnesia:~$ sudo -shx ~i2pd/[pn][e]*
sudo: unable to resolve host x: Temporary failure in name resolution
[sudo] password for amnesia:
/bin/bash: line 1: ~i2pd/[pn][e]*: No such file or directory
amnesia@amnesia:~$

I will try to troubleshoot further to see if it has to do with NetworkManager or some other OS thing. Currently my suspicion is the router 60%. Check also the reviews from the snapstore. I have older routers that are running fine at 60% tunnel building so I do not suspect any general attack.

Show output while i2pd running:
$ top -b | head
# du -shx ~i2pd/[pn][e]*

I had a Snap Store router installed with gnome-software Ubuntu Jammy stop building tunnels after 10 hours. I can't post logs because the whole test OS died. I saw a lot of negative reviews too. Can anybody confirm the story?

I tried another router with the github binary install and a similar thing happened.(Ubuntu Jammy)

Добавлено

Русскоязычные адаптации материалов по общей-семантике
http://generalsemantic.i2p/

Баннер - http://333.i2p/files/logo_time.png

It might be from the French riots. They attacked Tor and Tor downloads/updates. Even this site has login problems. They started to booby trap more than a few weeks ago. Usually things show on reboot if no-UEFI was used. I'm nowhere near the riots and I lost a lot of French based software. Try to see if Mik's tobrowser-downloader works. That is a sure test....

Every second, Pidgin attempts a multicast to 224.0.0.251 (UDP) port 5353. There is nothing about this on the web that I could find.

I not running Pidgin with the --force-online option.

Maybe I will try running with the --debug option.

I block that address because I don't trust all devices on my LAN. I would rather disable this multicast in Pidgin. And not stop getting the messages from the firewall when app does something weird like this.

Anyone know how to fix this broadcasting problem?

Self signed certificates are always a problem in Android. You can try this:
https://stackoverflow.com/questions/1217141/sel...

I faced this issue yesterday, while migrating our company's RESTful API to HTTPS, but using self-signed SSL certificates.

I've looking everywhere, but all the "correct" marked answers I've found consisted of disabling certificate validation, clearly overriding all the sense of SSL.

I finally came to a solution:

Create Local KeyStore

To enable your app to validate your self-signed certificates, you need to provide a custom keystore with the certificates in a manner that Android can trust your endpoint.

The format for such custom keystores is "BKS" from BouncyCastle, so you need the 1.46 version of BouncyCastleProvider that you can download here.

You also need your self-signed certificate, I will assume it's named self_cert.pem.

Now the command for creating your keystore is:

<!-- language: lang-sh -->

$ keytool -import -v -trustcacerts -alias 0 \
-file *PATH_TO_SELF_CERT.PEM* \
-keystore *PATH_TO_KEYSTORE* \
-storetype BKS \
-provider org.bouncycastle.jce.provider.BouncyCastleProvider \
-providerpath *PATH_TO_bcprov-jdk15on-146.jar* \
-storepass *STOREPASS*

PATH_TO_KEYSTORE points to a file where your keystore will be created. It MUST NOT EXIST.

PATH_TO_bcprov-jdk15on-146.jar.JAR is the path to the downloaded .jar libary.

STOREPASS is your newly created keystore password.

Include KeyStore in your Application

Copy your newly created keystore from PATH_TO_KEYSTORE to res/raw/certs.bks (certs.bks is just the file name; you can use whatever name you wish)

Create a key in res/values/strings.xml with

<!-- language: lang-xml -->

<resources>
...
<string name="store_pass">*STOREPASS*</string>
...
</resources>

Create a this class that inherits DefaultHttpClient

import android.content.Context;
import android.util.Log;
import org.apache.http.conn.scheme.PlainSocketFactory;
import org.apache.http.conn.scheme.Scheme;
import org.apache.http.conn.scheme.SchemeRegistry;
import org.apache.http.conn.ssl.SSLSocketFactory;
import org.apache.http.impl.client.DefaultHttpClient;
import org.apache.http.params.HttpParams;

import java.io.IOException;
import java.io.InputStream;
import java.security.*;

public class MyHttpClient extends DefaultHttpClient {

private static Context appContext = null;
private static HttpParams params = null;
private static SchemeRegistry schmReg = null;
private static Scheme httpsScheme = null;
private static Scheme httpScheme = null;
private static String TAG = "MyHttpClient";

public MyHttpClient(Context myContext) {

appContext = myContext;

if (httpScheme == null || httpsScheme == null) {
httpScheme = new Scheme("http", PlainSocketFactory.getSocketFactory(), 80);
httpsScheme = new Scheme("https", mySSLSocketFactory(), 443);
}

getConnectionManager().getSchemeRegistry().register(httpScheme);
getConnectionManager().getSchemeRegistry().register(httpsScheme);

}

private SSLSocketFactory mySSLSocketFactory() {
SSLSocketFactory ret = null;
try {
final KeyStore ks = KeyStore.getInstance("BKS");

final InputStream inputStream = appContext.getResources().openRawResource(R.raw.certs);

ks.load(inputStream, appContext.getString(R.string.store_pass).toCharArray());
inputStream.close();

ret = new SSLSocketFactory(ks);
} catch (UnrecoverableKeyException ex) {
Log.d(TAG, ex.getMessage());
} catch (KeyStoreException ex) {
Log.d(TAG, ex.getMessage());
} catch (KeyManagementException ex) {
Log.d(TAG, ex.getMessage());
} catch (NoSuchAlgorithmException ex) {
Log.d(TAG, ex.getMessage());
} catch (IOException ex) {
Log.d(TAG, ex.getMessage());
} catch (Exception ex) {
Log.d(TAG, ex.getMessage());
} finally {
return ret;
}
}
}

Now simply use an instance of **MyHttpClient** as you would with **DefaultHttpClient** to make your HTTPS queries, and it will use and validate correctly your self-signed SSL certificates.

HttpResponse httpResponse;

HttpPost httpQuery = new HttpPost("https://yourserver.com";);
... set up your query ...

MyHttpClient myClient = new MyHttpClient(myContext);

try{

httpResponse = myClient.(peticionHttp);

// Check for 200 OK code
if (httpResponse.getStatusLine().getStatusCode() == HttpURLConnection.HTTP_OK) {
... do whatever you want with your response ...
}

}catch (Exception ex){
Log.d("httpError", ex.getMessage());
}