Gravelrash Wrote: ------------------------------------------------------- > as much as i adore Android, it should only ever be > considered an "entertainment system" not an > "operating system" > > @bodhi & all > The vector vulnerability exists in all kernels > from 3.6 upwards, so it is best to add the "fix" > outlined above toby feas - Off-Topic
Is this something we can fix on our own or do we need a patch from bodhi for the kernel? you are required to append the following to /etc/sysctl.conf: net.ipv4.tcp_challenge_ack_limit = 999999999 Once done, use sysctl -p to activate the new rule. You need to perform root to do this. https://thehackernews.com/2016/08/linux-tcp-packet-hacking.htmlby feas - Off-Topic
Well I have not been able to get fail2ban nor sshguard to work with the log files to block failed access attempts. I have made several attempts at modifying the regex for fail2ban and even checked it against a web regex checker that works but fail2ban still will not block the attempts with the added auth* string in the log files. What I have done is made some new iptable rules: Chain INPUTby feas - Off-Topic
I have been having a problem getting fail2ban to read my log file so it can block unauthorized ssh attempts due to the log format. Jul 31 03:29:45 deb-pogo auth.info sshd[2753]: Did not receive identification string from 163.172.198.246 Jul 31 03:29:45 deb-pogo auth.info sshd[2754]: reverse mapping checking getaddrinfo for 163-172-198-246.rev.poneytelecom.eu [163.172.198.246] fai$ Jul 31 0by feas - Off-Topic
Thanks for pulling my head out yet again1 I really would like to make a donation, do you have a donation page or pm me an address that I can send a donation too? You have really gone beyond helpful and I know there are others things you like to spend your time doing. #### EDIT #### You SIR! Are a ROCK STAR! All set now.by feas - uBoot
Had to play with the setenv variables as I got various errors but I am in as root now. So do I redo your uboot http://forum.doozan.com/read.php?3,12381 again?by feas - uBoot
This u-boot doesn't have usb commands like the other did. U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 128MB DRAM Totalby feas - uBoot
bodhi Wrote: ------------------------------------------------------- > Ok so do you have a log of what you did? It is all past the history limits. I left off from: QuoteBodhi Try this: reboot, interrupt serial console and setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; if run bootcmd_exec; then echo Booting with $bootdev ... ; else run pogo_bootcmd; fi; reby feas - uBoot
I understand but it is not like I am trying to see what things do willy nilly. I am just following the guides to get the system upgraded. Even my serial interface seems to be flaky at times. I type printenv and it will say "Unknown command 'printenv' - try 'help'" I will just keep googling if I can find the address to load the files to from nand. May wantby feas - uBoot
yes I can load to the kwb file to 0x800000 but not sure where to load anything else to fix the error for the kernel. I think all those writes to nand got messed up from going to the 2.82 rescue to v2 and then yours again since nothing was working.by feas - uBoot
What I posted is what I get usb or not. So I think I need to tftpboot the files to nand from uboot to fix the corrupt image. I do not get a shell or login prompt.by feas - uBoot
So if I was not being a pain before this will ensure it. I tried to compile the 2.8.2 rescue but there were problems with making it so I did not load it and went back to Bodhi's http://forum.doozan.com/read.php?3,12381 and had problems again. I am not sure if I have a problem with the serial connection not being secure enough and caused the file to become corrupt but this is what I get.by feas - uBoot
thanks nice additionby feas - Debian
thanks, it compiled with some errors so I will see about the other.by feas - Rescue System
So I downloaded and ran the process for: (or for V2.8.2 use this link : https://dl.dropbox.com/u/1015928/Kirkwood/rescue/RescueV2.8.2-10292012.tar.gz == but change commands for flashing accordingly !) now I am getting ready to build using: mkdir rescuebuilddir cd rescuebuilddir wget http://buildroot.uclibc.org/downloads/buildroot-2010.08.tar.gz tar zxf buildroot-2010.08.tar.gz wgetby feas - Rescue System
Need some rest before i give it a go. will let you know and thanksby feas - uBoot
Thanks! I will give it a go and let you know. Sorry to be pain. EDIT### It did not write to /var/log/auth.log I just changed it back and will use rc.local.by feas - Debian
So the above gave me some errors and I found: Boot and interrupt serial console, setenv pogo_bootcmd 'if fsload uboot-original-mtd0.kwb; then go 0x800200; fi' run pogo_bootcmd See if it boots back into Pogo OS. from http://forum.doozan.com/read.php?4,23425,25627#msg-25627 and all is right in the world. I then reboot and I have the same problem again. So I setenby feas - uBoot
that is how my E02 has to be or i get an error: "variable does not star with 'mtdparts'"by feas - uBoot
syslogd -h syslogd: invalid option -- 'h' BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) multi-call binary. Usage: syslogd System logging utility (this version of syslogd ignores /etc/syslog.conf) -n Run in foreground -O FILE Log to FILE (default:/var/log/messages) -l N Log only messages more urgent than prio N (1-8) -S Smaller output -R HOST[:PORT] Log to HOST:PORby feas - Debian
If you set it in busybox I would have to compile my own busybox with the settings to to write a log file elsewhere right? Which may explain why I do not see a syslogd.conf anywhere to modify it. So am I Cold... Hot... How do you remember to breathe? EDIT: So the work around I came up with is to add the following to rc.local: /sbin/syslogd -O /var/log/auth.log || exit 1 Is there a betby feas - Debian
I have been trying to set up fail2ban and it turns out that login attempts are not being logged to /var/log/auth.log cause it does not exist. Do you have this info going someplace else I can set fail2ban to examine?by feas - Debian
http://www.theinquirer.net/inquirer/news/2466107/https-attack-airs-browsing-habits-of-linux-mac-and-windows-usersby feas - Off-Topic
bodhi Wrote: ------------------------------------------------------- > feas, > > Everything looks great! phew! > > Now about booting back to stock OS when the USB > drive is unplugged or corrupted. Recall you've > save your current_envs.txt when upgrading u-boot? > The saved envs in that file should be used to > restore the settings to boot stock.by feas - uBoot
bodhi Wrote: ------------------------------------------------------- > feas, > > Your rootfs still have problem. It booted, but not > the way you want to set it up. > > > [ 0.000000] Kernel command line: > console=ttyS0,115200n8 earlyprintk root=/dev/sda1 > rootdelay=10 > > > > When you boot with the new u-boot and its default > envsby feas - uBoot
bodhi Wrote: > > It's UART booting. > > > Yes. But the Pogo E02 does not support UART > booting, so you have found that and use regular > serial console on the other thread. I was referring to the modems that I mentioned previously. I read about the UART was not for the E02 and used the one below that for my plug.by feas - Off-Topic
here is the log with the new usb: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700) Pogo E02 SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 128 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 3 USB Device(s) found scanning usby feas - uBoot
So the dist-upgrade broke several setting on the E02 for me. How am I suppose to handle upgrades in the future to stop this from happening again?by feas - uBoot
Ok got it to boot!!! The file over ftp did transfer but that did not fix the issue Here is what I did: mtdparts had an extra "mtdparts=" so reset that env The partitions were wrong so I wrote the file on the usb from my laptop to correct [ 1.749193] 0x000000000000-0x000000100000 : "u-boot" [ 1.755382] 0x000000100000-0x000000500000 : "uImage"by feas - uBoot
@ Ray Thanks for looking for the firmware. I had already downloaded them and looked around. Seems to me they are all set to up to compile when you load them. What I am trying to figure out is can I just drop in ssh or something and how to get it to enable a root shell which does not exist currently. It has a timer count down to booting but as it stands now I cant seem to find a way to interupt tby feas - Off-Topic