Super moderator
  • Content count

  • Joined

  • Last visited

About zador.blood.stained

  • Rank
    Embedded member

Profile Information

  • Gender

Recent Profile Visitors

2045 profile views
  1. Or at the server side (nginx). As a bonus it's easy to add/remove servers at any point without breaking the clients or forcing them to update server addresses.
  2. Packages are signed, package lists are signed and public key is imported at the image creation stage. Adding HTTPS will only change the list or package signature error into invalid HTTPS certificate error in case is redirected to a 3rd party server.
  3. Not exactly necessary, package signing provides a good security by default:
  4. KRACK WPA2 Wi-Fi vulnerability

    The most important CVEs affect clients (= the wpasupplicant package) and updates for it are already available from upstream Debian and Ubuntu repositories. For people running access point hostapd has some minor problems too. Standard package was already patched (but the repository was not updated yet as of now) and hostapd-realtek package was not patched.
  5. Debian Stretch Porting and Optimizations

    Rather this one:
  6. Armbian on a custom board - Issues

    If it's something based on already supported (and well supported SoC like Allwinner A20) - you won't encounter any significant issues, you will only have to adapt your board configuration and patches from time to time when syncing your repository fork with the main one. If it's something not supported already - the main issue would be the quality of vendor provided SDK, and the issue that comes after that - integrating the vendor provided stuff with our build scripts. Already partially answered by @Tido - no onboard firmware like BIOS/EFI (with rare exceptions), so you have to provide board specific bootloader, kernel and DT and hope that version you've been given works well with the userspace that you want (good luck & have fun running Debian Stretch on kernel 3.4 or compiling Amlogic 3.1x kernel with namespaces and AppArmor support without patching it) Integrated build system that works pretty well (especially if you have enough RAM, disk space and a stable Internet connection). For a private board other advantages (like kernel and u-boot package updates) may not apply. Bootloader (i.e. u-boot) and kernel are critical components (of the SDK/board support package), you don't have to customize anything else until you are optimizing the performance and improving user experience.
  7. solved KRACK WPA2 Wi-Fi vulnerability

    To include this patch from OpenWRT/LEDE: There is also a second customized version with some Realtek specific drivers("hostapd-realtek"), not sure if it's relevant only for the legacy kernel or is required on the mainline too. Yes, I'll try to find the new patches and hopefully they apply on newer sources too.
  8. Debian Stretch Porting and Optimizations

    This (and similar relocation related issue on XU4/HC1 which killed UAS) should be hopefully fixed. Other kernel configs may have to be changed too in the future.
  9. Debian Stretch Porting and Optimizations

    Are you sure? I don't see any changes in the stretch network-manager changelog I may have found a kernel option that may fix that, will commit changes soon
  10. Quick Pinebook Preview / Review

    Did anyone test Icenowy's linux-4.13.y branch? I'm experiencing weird issues like "unhandled level 2 translation fault" in standard apps (bash, python, sed) and I'm not sure how to interpret it. Don't remember any similar issues on the Pine64 and SoPine, but I'll test it with the current sources in a few days.
  11. Serial Converter USB to RS485 is not available

    @martinayotte Tinkerboard images are not compatible with Rock64 ones, so there are no Ayufan's images for it
  12. Serial Converter USB to RS485 is not available

    but not to Rockchip configs, so somebody has to add it and push the changes to our repository.
  13. Gadget mode hid support.

    In the sunxi-next kernel both legacy g_hid and libcomposite hid gadgets are enabled, so we have done everything that is under our control to make things work. I compiled a fresh 4.13.7 kernel, compiled this library and tried to test it root@orangepiplus2e:~# modprobe libcomposite root@orangepiplus2e:~# cd libusbgx/examples/ root@orangepiplus2e:~/libusbgx/examples# ./show-gadgets root@orangepiplus2e:~/libusbgx/examples# ./gadget-hid root@orangepiplus2e:~/libusbgx/examples# ./show-gadgets ID 1d6b:0104 'g1' UDC bcdUSB 2.00 bDeviceClass 0x00 bDeviceSubClass 0x00 bDeviceProtocol 0x00 bMaxPacketSize0 64 idVendor 0x1d6b idProduct 0x0104 bcdDevice 0.01 Language: 0x409 Manufacturer Foo Inc. Product Bar Gadget Serial Number 0123456789 Function, type: hid instance: usb0 dev 242:0 protocol 1 report_desc 5196a115719e029e7150251751958812951758813955751581912959129517539139567581502565571902965810c0 report_length 8 subclass 0 Configuration: 'The only one' ID: 1 MaxPower 2 bmAttributes 0x80 Language: 0x409 configuration 1xHID some_name -> hid usb0 root@orangepiplus2e:~/libusbgx/examples# ls /dev/hid* /dev/hidg0 root@orangepiplus2e:~/libusbgx/examples# On the other side of the USB connection ➜ armbian git:(master) ✗ % lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M |__ Port 10: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M ➜ armbian git:(master) ✗ %
  14. Problems loading modules

    AFAIK you need to set the LOCALVERSION too (on the command line) to make the new modversion compatible with the old one.