encryption – How are passwords stored in the database of a decentralized peer to peer system?

I want to use username and password instead of public key cryptography for a decentralized peer-to-peer application, but since the passwords are stored on users’ computers, there is a possibility of being stolen. How do I store the passwords securely?

And how do I give permission safely? How can I prevent someone else from gaining permission unfairly?

reactjs – npm peer dependencies for react-helmet-async package gives error using React 17

For a React 17 project, bootstrapped with create-react-app, I want to use the react-helmet-async package.
This project has the following peer dependencies, located in the package.json file:

  "peerDependencies": {
    "react": "^16.6.0",
    "react-dom": "^16.6.0"
  },

When trying to install the package, the following error appears:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: project@1.0.0
npm ERR! Found: react@17.0.1
npm ERR! node_modules/react
npm ERR!   react@"^17.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.6.0" from react-helmet-async@1.0.7
npm ERR! node_modules/react-helmet-async
npm ERR!   react-helmet-async@"^1.0.7" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/bas/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/bas/.npm/_logs/2021-02-11T13_55_56_813Z-debug.log

As far as I understand, the react-helmet-async package requires React ^16.6.0 for projects using this package. I can use the --force option, which removes the error, but when I try to do an npm update it keeps recurring.

I tried adding resolutions in my package.json, trying to force the package to use the React version I’m using. Before running a npm install or npm update, I ran npx npm-force-resolutions.

  "resolutions": {
    "react-helmet-async/react": "^17.0.1"
  }

This unfortuntaly did not work. Is there any way, without downgrading to React 16, to still use this package without receiving errors in my console? Also, am I misunderstanding something about peer dependencies?

routing – Wireguard client communication without peer key via 1 router server

I have this setup:

—server 1 config—

[Interface]
Address = 10.200.200.1/24
ListenPort = 6666
PrivateKey = server_private_key

[Peer]
PublicKey = client1_public_key
AllowedIPs = 10.200.200.2/32
PersistentKeepalive = 21

[Peer]
PublicKey = client2_public_key
AllowedIPs = 10.200.200.4/32
PersistentKeepalive = 21

— client 1 config—

[Interface]
Address = 10.200.200.2/24
PrivateKey = client1_private_key
DNS = 10.200.200.1

[Peer]
PublicKey = server_public_key
Endpoint = server_ip:6666
AllowedIPs = 10.200.200.1/32
PersistentKeepalive = 21

— client 2 config—

[Interface]
Address = 10.200.200.4/24
PrivateKey = client2_private_key
DNS = 10.200.200.1

[Peer]
PublicKey = server_public_key
Endpoint = server_ip:6666
AllowedIPs = 10.200.200.1/32
PersistentKeepalive = 21

I can ping server from client1 and client2, but i can’t ping client1 from client2 and client2 from client1.

Is there a way for client1 ping client2 without adding client2 key to client1 config, since this will make addding client much harder. For example, if i add 1 new client when having 5 clients, all of the config must be changed.

iCloud Keychain issue ? (otctl : excluded peer)

I have recurring problems with my iMac that result in a kernel_task spinning at 990% CPU making it almost unusable.
I suspect that this is linked to a problem with my Apple account failing to synch, precisely the account I use for the App Store, (which btw results in a error message in console )

Account <MyAppStoreAccount> is not valid, missing altDSID! 

Looking for help on the internet about altDSID I found a reference to the otcltl command why gives status on iCloud keychain syncing. When I run the command I get a very strange answer :

/usr/sbin/otctl status

Trusted peers (by me):
Self SHA256:<somekey> 0= hw:'iMac19,1' name:'' serial: '<MySerialNumber>' os:'macOS 19.6.0 (19H114)' epoch:1

Excluded peers (by me):
Peer: SHA256:<someotherkey> hw:'iMac19,1' name:'' serial: '< MySerialNumber>' os:'macOS 19.6.0 (19H114)' epoch:1

In other words, my machine is at the same time trusted and excluded from keychain icloud with different keys. (my other devices, iPad,iphone,TV, etc… also appear has trusted peers)

This seems quite strange to me. This machine has only one SSD with one OS on it (Catalina), and an external ssd for backup with time machine.

I did not find either any info on the internet about otctl

Any idea if this is normal ?

I have downloaded Xcode and built a small iOS app locally, but apart of that, my use of this Mac is fairly standard.

networking – Private Connection (Peer to Peer/Headless?) to ESXi 6.5 on IBM System x3550

Windows 10 Workstation
IBM System x3550 with ESXi 6.5 (Installed) at DCUI.
Ethernet cable from ESXi server to Workstation.

Server IP: 192.168.50.100 (Static) Webaddress given http://192.168.50.100/
Workstation USB to Ethernet IP: 192.168.50.50 (Static)
Mask: /24

I am unable to browse to the web interface for this ESXi server.
I can not ping the server IP.

I am new to ESXi and have looked around. The x3550 is verified to
work with ESXi 6.5. I got this server to install this on. Have not
done anything to the server other than install another CPU and more RAM.
Then I installed ESXi 6.5.

I am connected to interface 3 on the server and it shows “UP” in the config.
I have read that the only way to manage ESXi 6.5 is the web client. Tools are
no longer supported.

What am I missing here?

Magento 2 stream_socket_enable_crypto(): Peer certificate CN=`ns1004402.us’ did not match expected CN=smtp.office365.com

After installing SMTP, I am getting below error.
Warning: stream_socket_enable_crypto(): Peer certificate CN=ns1004402.us' did not match expected CN=smtp.office365.com’ in /home/public_html/vendor/magento/zendframework1/library/Zend/Mail/Protocol/Smtp.php on line 207

Bitcoind gui client, wallet client with peer preference, node manager

yup, see what you mean. Hopefully my answer is not disappointing. It is to my knowledge not existant. I’d reason this way:
I don’t think it’s the application, which should secure the network layer. Vice versa is the way to go on (layered approach). Create a secure network layer, and run the app on top of it. Otherwise all apps would build their own security layer, and I doubt there are enough security specialists…

The layers of the underlying OS allows to achieve security.

A very secure ‘remote wallet’ GUI:

define secure 🙂 Well, why not tunnel X over a VPN or through ssh?

A bitcoind full node GUI manager:

is the same.

A wallet manager application:

again, security built into the app is against principle of layers. You can tell your full node, from which IP to connect.

What does it mean that Ikev1 (IPSec) protects peer identities in main mode?

Does it mean that the source IP is replaced with something else (like if in IP spoofing) so intermediate routers don’t know who is sending the packet?

Buy Ready Zarfund | Peer to Peer   – HYIPs

We are Zarfund, Member to Member Donation Website,BTC Mining, Ads Clicking and BTC Doubler investment website seller and can make btc doubler ready website within 24 hours at very low price.
We offer all in one ready website with free domain and hosting with lifetime free support
(i) Investment Script
(ii) Domain and hosting
(iii) Logo
(iv) Design
For detail you can check our website newwebmaker.com
Skype: live:Newwebmaker.com
Email: Newwebmaker.com@gmail.com
Email: Support@Newwebmaker.com

vpn – Connection reset by peer unless immediately after target machine reboots

I have a strange networking problem. I have a VPN setup on udp:1195 on an office (changed the port from 1194).

The VPN server is 10.9.0.1, my client receives 10.9.0.2 when connected.

I can ping LAN servers (10.217.50.0/24) from my home when VPN connected.

I can ping my VPN client from the lan servers (10.9.0.2).

I can always ssh from LAN server to VPN client. (on 10.217.50.169 >> ssh 10.9.0.2)

I can ONLY ssh from vpn client to lan server if the target server just rebooted. (on 10.9.0.2 >> ssh 10.217.50.169)

If I wait more than a few seconds after the machine has rebooted, I get the following error:

ssh user1@10.217.50.169
kex_exchange_identification: read: Connection reset by peer
Connection reset by 10.217.50.169 port 22

The router @ work is a Verizon Fios G1100. I have a route on it to allow 10.217.50.0/24 to see 10.9.0.0/24.

Any Ideas?

I’m guessing I’m getting blocked by some firewall rule in the router a few seconds after the machine comes online.

It seems that this router doesn’t have an option for packet filtering on the firewall web configuration. I do have ssh access to the firewall and I’ve confirmed from my vpn, I can connect to the VPN gateway 10.9.0.1 and the router 10.217.50.1.