Friday, June 14, 2019
Wireguard on Raspberry Pi 2 B+
Probably after the installation you will not be able to run wireguard due missing modules in /lib/modules.
Verify by issuing:
sudo modprobe wireguard
modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.19.50-v7+
[SOLUTION :]
sudo dpkg-reconfigure wireguard-dkms
sudo modprobe wireguard
pip error - cannot import main [SOLVED] + module has no attribute SSL_ST_INIT
Set python2.7 as default:
select python2.7
Remove
Reinstall it:
Check the
Do not upgrade
sudo update-alternatives --config python
select python2.7
Remove
pip:sudo python -m pip uninstall pip
sudo apt purge --autoremove python-pip
Reinstall it:
sudo apt install python-pip
Check the
pip --version:pip 9.0.1 from /usr/lib/python2.7/dist-packages (python 2.7)
Do not upgrade
pip to the latest version.In case of the following error:
AttributeError: 'module' object has no attribute 'SSL_ST_INIT'
sudo python -m easy_install --upgrade pyOpenSSL
Wednesday, June 5, 2019
hacked.camera
Hundreds of brands of security cameras, baby monitors, and
“smart” doorbells have serious vulnerabilities that allow hackers to
hijack devices and spy on their owners.
Affected devices use “peer-to-peer” features (also known as “P2P”) that allow users to connect to their devices the moment they come online. Hackers are able to exploit flaws in these features to rapidly find vulnerable cameras, then launch attacks to access them – all without the owner’s knowledge.
Over 2 million vulnerable devices have been identified on the Internet, including those distributed by HiChip, TENVIS, SV3C, VStarcam, Wanscam, NEO Coolcam, Sricam, Eye Sight, and HVCAM. Affected devices use a component called iLnkP2P. Unfortunately, iLnkP2P is used by hundreds of other brands as well, making identification of vulnerable devices difficult.
A UID will look like:
In this example,
If disposing of the device is not possible, the P2P functionality may be effectively neutered by blocking outbound traffic to UDP port 32100. This will prevent devices from being accessed from external networks via P2P (though local access will still work).
iLnkP2P is one of several P2P solutions utilized by device manufacturers. It was developed by Shenzhen Yunni Technology Company, Inc.
Affected devices use “peer-to-peer” features (also known as “P2P”) that allow users to connect to their devices the moment they come online. Hackers are able to exploit flaws in these features to rapidly find vulnerable cameras, then launch attacks to access them – all without the owner’s knowledge.
Over 2 million vulnerable devices have been identified on the Internet, including those distributed by HiChip, TENVIS, SV3C, VStarcam, Wanscam, NEO Coolcam, Sricam, Eye Sight, and HVCAM. Affected devices use a component called iLnkP2P. Unfortunately, iLnkP2P is used by hundreds of other brands as well, making identification of vulnerable devices difficult.
Am I affected?
Vulnerable devices will have a special serial number known as a UID, which is typically printed on a label somewhere on the device.A UID will look like:
FFFF-123456-ABCDEIn this example,
FFFF is the device’s prefix. Devices with the following prefixes are known to be vulnerable:| AID | AJT | AVA | BSIP | CAM |
| CPTCAM | CTW | DFT | DFZ | DYNE |
| EEEE | ELSA | ESN | ESS | EST |
| FFFF | GCMN | GGGG | GKW | HDT |
| HHHH | HRXJ | HVC | HWAA | HZD |
| HZDA | HZDB | HZDC | HZDN | HZDX |
| HZDY | HZDZ | IIII | IPC | ISRP |
| JWEV | KSC | MCI | MCIHD | MDI |
| MDIHD | MEG | MEYE | MGA | MGW |
| MIC | MICHD | MMMM | MSE | MSEHD |
| MSI | MSIHD | MTE | MTEHD | MUI |
| MUIHD | NIP | NIPHD | NPC | NTP |
| OBJ | OPCS | OPMS | PAR | PARC |
| PCS | PHP | PIO | PIPCAM | PIX |
| PNP | PSD | PTP | QHSV | ROSS |
| SID | SIP | SXH | TIO | TSD |
| UID | VIO | VSTD | VSTF | WBT |
| WBTHD | WNS | WNSC | WXH | WXO |
| XDBL | XTST | ZES | ZLD | ZSKJ |
| ZZZZ |
What can I do?
Ideally, buy a new device from a reputable vendor. Research suggests that a fix from vendors is unlikely, and these devices are often riddled with other security problems that put their owners at risk.If disposing of the device is not possible, the P2P functionality may be effectively neutered by blocking outbound traffic to UDP port 32100. This will prevent devices from being accessed from external networks via P2P (though local access will still work).
More Information
What is P2P? What is iLnkP2P?
P2P is a feature included in many devices that allows them to be accessed without any manual configuration. By using a special serial number known as a UID, users may instantly connect to their device from their phone or computer. A main selling point of P2P devices is that they do not require port forwarding or dynamic DNS in order to be accessed, and are capable of overcoming NAT and firewall scenarios automatically.iLnkP2P is one of several P2P solutions utilized by device manufacturers. It was developed by Shenzhen Yunni Technology Company, Inc.
What is CVE-2019-11219?
CVE-2019-11219 refers to an enumeration vulnerability in iLnkP2P that allows attackers to rapidly discover devices that are online. Due to the nature of P2P, attackers are then able to directly connect to arbitrary devices while bypassing firewall restrictions.What is CVE-2019-11220?
CVE-2019-11220 refers to an authentication vulnerability in iLnkP2P that allows attackers to intercept connections to devices and perform man-in-the-middle attacks. Attackers may use this vulnerability to steal the password to a device and take control of it.Are all P2P devices vulnerable to these issues?
No. There are several different P2P solutions in use by different vendors. These issues are specific to devices that use iLnkP2P.I don’t know my UID. Is there another way to determine if I am affected?
Devices that use the following Android apps may be vulnerable:- HiChip: CamHi, P2PWIFICAM, iMega Cam, WEBVISION, P2PIPCamHi, IPCAM P
- VStarcam: Eye4, EyeCloud, VSCAM, PnPCam
- Wanscam: E View7
- NEO: P2PIPCAM, COOLCAMOP
- Sricam: APCamera
- Various: P2PCam_HD
Who are you?
I am PaulSunday, May 26, 2019
Install VNC on Ubuntu 18.04 for RDP from Windows
Install Xfce on your server:
/etc/systemd/system/vncserver@.service
sudo apt install xfce4 xfce4-goodies xorg dbus-x11 x11-xserver-utils
sudo apt install tigervnc-standalone-server tigervnc-common
Next setup a password for vnc login:
$ vncpasswd
$ ls -l ~/.vnc/
sudo nano /etc/systemd/system/vncserver@.service
/etc/systemd/system/vncserver@.service
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target
[Service]
Type=simple
User=linuxize
PAMName=login
PIDFile=/home/%u/.vnc/%H%i.pid
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill :%i > /dev/null 2>&1 || :'
ExecStart=/usr/bin/vncserver :%i -geometry 1440x900 -alwaysshared -fg
ExecStop=/usr/bin/vncserver -kill :%i
[Install]
WantedBy=multi-user.target VNC is not an encrypted protocol and can be subject to packet sniffing.
The recommended approach is to create an SSH tunnel that will securely
forwards traffic from your local machine on port 5901 to the server on
the same port.Sunday, May 19, 2019
Samsung A3 SM-A310F - FRP Cloud Lock
Разблокировка FRP
1. Flash Service Image ( Сервисная прошивка )
- Odin -- Use the AP or PDA in older version
- boot phone into Download Mode ( blue screen - volDown+Home+Pwr ; rel; volUp )
2. Enable USB debugging on Phone0
> Settings > SW info > tap 10x times Build Number >> DevOps mode
3. Power phone off
-- start to Download Mode again
4. Flash Stock ROM
-- Choose correct country + provider
-- https://www.updato.com
5. Enable OEM Unlock
-- Settings > Developer Mode > Enable OEM Unlock (Disable device security)
now you can flash TWRP and root your A3 .. or keep it in Stock and Encrypt it ;)
6. Flash TWRP Recovery image
Android 7.0+ on Samsung with ROOT -- disable encryption
Разблокировка FRP
1. Flash Service Image ( Сервисная прошивка )
- Odin -- Use the AP or PDA in older version
- boot phone into Download Mode ( blue screen - volDown+Home+Pwr ; rel; volUp )
2. Enable USB debugging on Phone0
> Settings > SW info > tap 10x times Build Number >> DevOps mode
3. Power phone off
-- start to Download Mode again
4. Flash Stock ROM
-- Choose correct country + provider
-- https://www.updato.com
5. Enable OEM Unlock
-- Settings > Developer Mode > Enable OEM Unlock (Disable device security)
now you can flash TWRP and root your A3 .. or keep it in Stock and Encrypt it ;)
6. Flash TWRP Recovery image
Android 7.0+ on Samsung with ROOT -- disable encryption
Разблокировка FRP
Friday, May 10, 2019
webmin install on ubuntu
First download the latest package:
wget https://www.webmin.com/download/deb/webmin-current.deb
Install Debian package installer :
sudo apt install gdebi
And run it (gdebi-gtk for GUI):
sudo gdebi webmin-current.deb
When install is done visit:
https://localhost:10000/
Login as root with your root password, or as any user who can use sudo
Unix tar/gzip format
https://www.webmin.com/download/webmin-current.tar.gz
RPM suitable for Redhat, Fedora, CentOS, SuSE or Mandrake Linux
https://www.webmin.com/download/rpm/webmin-current.rpm
Debian package suitable for Debian, Ubuntu or other derived Linux
https://www.webmin.com/download/deb/webmin-current.deb
Solaris package format
https://www.webmin.com/download/solaris-pkg/webmin-current.pkg.gz
Wednesday, April 3, 2019
Error: 0x80070002 solution (SWbemObjectEx) - regedit
If you receive the error below - it means you have used a software to activate Windows without a valid license.
The file doesn't exist in default Win install.
c:\Windows\System32>cscript slmgr.vbs /ato
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Activating Windows(R), Professional edition () ...
Error: 0x80070002 The system cannot find the file specified. (SWbemObjectEx)
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.
Activating Windows(R), Professional edition (
Error: 0x80070002 The system cannot find the file specified. (SWbemObjectEx)
- it means you have used a software to activate Windows without a valid license. The file doesn't exist in default Win install.
Delete the below key from registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\SppExtComObj.exe
this will resolve the issue.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\SppExtComObj.exe
this will resolve the issue.
Subscribe to:
Posts (Atom)