**** BEGIN LOGGING AT Fri Aug 18 03:00:01 2017
Aug 18 05:36:19 <vajb2> mission accomplished "uname -r 4.10.17"
Aug 18 06:00:29 <mva> hi there!
Aug 18 06:01:09 <mva> I've just updated CSSU to -thumb0 version, and my N900 is in reboot loop now :-/
Aug 18 06:01:56 <mva> well, it, at least, loads to the desktop, and reboots after few seconds
Aug 18 06:02:11 <mva> is it a way to repair it without reflashing?
Aug 18 06:03:17 <vajb2> mva, just a thought, but are you sure that your battery is fine?
Aug 18 06:03:58 <mva> well, it was okay before upgrade :)
Aug 18 06:03:59 <vajb2> because, i've heard that in a boot loop, n900 wont get past those 5 white dots
Aug 18 06:13:04 <mva> vajb2: well, I replaced the battery with another. Just in case. And it still loads to the desktop and reboots. By the way, it reboots *only* after loading to the desktop and doesn't reboot until I set up date and time. 
Aug 18 06:13:25 <mva> so, it's definitelly not a battery :-/
Aug 18 06:30:06 <sicelo> you might be running wrong kernel.
Aug 18 06:33:26 <freemangordon> sicelo: no way
Aug 18 06:33:44 <sicelo> ok 
Aug 18 06:34:21 <freemangordon> mva: using flasher, disable resets, so it wo't reboot when a "guarded" process fails, then check in syslog what happens and fix it
Aug 18 06:34:30 <freemangordon> *won't
Aug 18 06:40:05 <DocScrutinizer05> I can tell you what happens: segfauilts from wrong kernel
Aug 18 06:40:36 <DocScrutinizer05> what else could it be?
Aug 18 06:40:36 <freemangordon> could be
Aug 18 06:40:57 <freemangordon> some hildon-status-menu plugin misbehaving
Aug 18 06:41:11 <freemangordon> or some home widget
Aug 18 06:41:27 <DocScrutinizer05> hmm, how many are in thumb only?
Aug 18 06:41:34 <freemangordon> nothing
Aug 18 06:41:41 <DocScrutinizer05> what I thought
Aug 18 06:42:39 <DocScrutinizer05> mva: maybe you want to elaborate on details of >>I've just updated CSSU to -thumb0 version<<
Aug 18 06:42:41 <freemangordon> but I doubt it will boot to hildon with the wring kernel
Aug 18 06:42:50 <freemangordon> *wrong
Aug 18 06:42:59 <sicelo> i'm also interested to know. i experienced the exact same issue mva experiences. at that time, my N900 was in near-stock state (mid-June) as I had reflashed. unfortunatley i did not have a chance to test a lot of things, because i desperately needed a working phone
Aug 18 06:50:27 <mva> DocScrutinizer05: I don't know what details I can also provide :) I just have N900 with disabled wifi for many time (may be few months). Today I enabled wifi and it found the updates. When I looked on the version of the CSSU package, it was differ from installed version for only "-thumb0" suffix 
Aug 18 06:51:43 <sicelo> 0.o
Aug 18 06:51:58 <mva> by the way, yes, I was use "power" kernel (from the repos) before the update :-/
Aug 18 06:57:49 <DocScrutinizer05> ok, that's very starnge then
Aug 18 06:58:09 <DocScrutinizer05> please proceed as freemangordon suggested
Aug 18 07:02:51 <freemangordon> mva: did you happen to update something else besides cssu?
Aug 18 07:02:56 <freemangordon> like, u-boot?
Aug 18 07:03:34 <freemangordon> if you have u-boot installed ofc
Aug 18 07:04:27 <DocScrutinizer05> if only there were HAM logs ;-)
Aug 18 07:04:52 <freemangordon> :)
Aug 18 07:05:15 <freemangordon> however, I am going afk, bye
Aug 18 07:05:40 <sicelo> what info would we be looking for in HAM logs?
Aug 18 07:08:50 <mva> freemangordon: well, there was some packages too, but since n900 rebooted just after installing cssu, I think it doesn't upgraded them...
Aug 18 07:09:35 <mva> and, IIRC, there was no u-boot in that list
Aug 18 07:11:32 <mva> // by the way, I'm unsure if I had installed u-boot, but I do see some boot menu on the white background, that suggests recovery mode, after few boot-loops
Aug 18 07:17:41 <DocScrutinizer05> good, was already wondering why it doesn't come up. Though I wonder what's 'reboot' then. Should be a shell that shows up *instead* of reboot when max_restart exceeded for a process monitored by dmsetool
Aug 18 07:23:02 <mva> well, reboot looks like it is "reboot" command somewhere. I mean, it is not just a sudden reboot, but it behaves like when I rebooted device by myself: the led indicator indicates it with the white color, plus sound notification, plus UI freezes on a second right before the reboot...
Aug 18 07:23:59 <DocScrutinizer05> hmmm, that's really strange
Aug 18 07:29:25 <mva> aargh
Aug 18 07:30:05 <mva> making 0xFFFF work on a modern system without libusb0 is a hard quest :-/
Aug 18 07:30:39 <mva> so sad it is no 0xFFFF in the recovery image :-/
Aug 18 07:31:50 <mva> oh
Aug 18 07:31:55 <mva> it is :D
Aug 18 07:35:21 <DocScrutinizer05> don't know how a modern system would lack libusb
Aug 18 07:36:45 <DocScrutinizer05> building 0xFFFF was a matter of less than a minute on my system, incl git clone
Aug 18 07:37:53 <mva> some non-debian/non-rh distributions dropped off libusb0 and ships libusb0-compat (wrapper on libusb1) instead
Aug 18 07:38:42 <mva> and 0xFFFF from git refuses to work with it (because of the timeout issues)
Aug 18 07:38:50 <DocScrutinizer05> http://paste.ubuntu.com/25337994
Aug 18 07:39:14 <mva> and somewhy I can't LD_PRELOAD libusb0 I taken from debian :-/
Aug 18 07:40:14 <mva> btw, also strange thing: 0xFFFF on the device (in the recovery image) says "Error: not implemented" when I trying to enable R&D mode :-/
Aug 18 07:40:41 <DocScrutinizer05> I wasted more than one of that 2 minutes with ls -l (alias l)
Aug 18 07:41:07 <mva> DocScrutinizer05: there is absolutelly no problem in *building* 0xFFFF for me
Aug 18 07:41:15 <mva> there is another problem:
Aug 18 07:41:26 <mva> > Error: You are trying to use broken libusb-1.0 library (either directly or via wrapper) which has slow listing of usb devices. It cannot be used for flashing or cold-flashing. Please use libusb 0.1.
Aug 18 07:41:42 <mva> and I'm trying to feed it with precompiled 0.1 from debian
Aug 18 07:42:18 <mva> well, anyway, there is the same 0.7 version on the device
Aug 18 07:42:28 <DocScrutinizer05> why don't you install libusb0.1 instead?
Aug 18 07:42:40 <mva> DocScrutinizer05: there is no libusb0 in the distro :-/
Aug 18 07:43:09 <mva> there is only libusb0-wrapper on libusb1 (which 0xFFFF refuses)
Aug 18 07:43:10 <DocScrutinizer05> that sucks big time
Aug 18 07:43:28 <DocScrutinizer05> so where from you take the precompiled .so then?
Aug 18 07:44:12 <DocScrutinizer05> unless you're _not_ using debian
Aug 18 07:44:18 <mva> well, as I said, there is the same 0.7 version of 0xFFFF on the device recovery image. and I guess, even if I'll get it to work on the PC, I'll get the same "Error: Not implemented" on trying to activate R&D mode :-/ 
Aug 18 07:44:36 <mva> DocScrutinizer05: here: https://packages.debian.org/sid/amd64/libusb-0.1-4/download
Aug 18 07:45:00 <DocScrutinizer05> and you can't install that?
Aug 18 07:45:07 <DocScrutinizer05> it seems it _is_ there
Aug 18 07:45:42 <mva> but, I'd like to understand why do on-device 0xFFFF says "not impemented" for now, instead of hacking on the PC version :-/
Aug 18 07:46:31 <DocScrutinizer05> on-device 0xFFFF ?
Aug 18 07:46:35 <DocScrutinizer05> what's that?
Aug 18 07:47:09 <DocScrutinizer05> you're pretty fuzzy, hard to understand your threads of thought
Aug 18 07:49:50 <DocScrutinizer05> I know it's an art to provide sufficient context without too much irrelevant info, but here you clearly provide too little context
Aug 18 07:51:00 <freemangordon_> mva: why don;t you just use flasher?
Aug 18 07:51:12 <mva> well, I enabled R&D mode, changed flags to `no-omap-wd,no-ext-wd,no-lifeguard-reset,no-usb-timeout`, and... is seems to stopped rebooting
Aug 18 07:51:21 <freemangordon_> mhm
Aug 18 07:51:35 <DocScrutinizer05> and what is "device recovery image", unless that's rescueOS in which case forget about using that for flashing
Aug 18 07:51:50 <freemangordon_> mva: now, check in syslog what is crashing
Aug 18 07:54:36 <DocScrutinizer05> for using flasher (or 0xFFFF) on device, you need to start some softupd service
Aug 18 08:00:06 <mva> uhm... there is no syslog in /var/log, `logread` says "logread: can't find syslogd buffer: No such file or directory", and I don't see any errors/segfaults in `dmesg` :-/
Aug 18 08:04:15 <mva> well, manual starting syslogd gives something, but I'm not sure it is related: https://gist.github.com/raw/ea9faf6cc897a5771d9e93ba02d3766d
Aug 18 08:05:22 <mva> and I don't know how to make syslogd start at boot time to make it log the real problem when in happens
Aug 18 08:11:47 <DocScrutinizer05> ^^^ http://paste.ubuntu.com/25338164
Aug 18 08:14:48 <DocScrutinizer05> never heard of logread
Aug 18 08:16:52 <DocScrutinizer05> Jan  1 06:13:46 Nokia-N900 user.crit browser[1721]: GLIB CRITICAL ** default - neteal_server_create_fork_async: assertion `server != NULL' failed
Aug 18 08:17:18 <DocScrutinizer05> for sure is no sign of a healthy system, at least by the frequency it shows up
Aug 18 08:17:58 <mva> DocScrutinizer05: shoud I make this script executable or it is okay to just put it there like many others (there is only n900-fmrx-enabler who have +x bit)
Aug 18 08:18:27 <DocScrutinizer05> should be fine in company with all the others
Aug 18 08:19:01 <DocScrutinizer05> I wonder why you don't already ahve it, it comes with isntallation of syslog/ksyslog
Aug 18 08:24:04 <mva> well, it it busybox's syslog plugin, but not a separate package. I'll install it now.
Aug 18 08:27:45 <freemangordon_> mva: please, install syslogd from repos and provide *full* boot log
Aug 18 08:29:01 <mva> yes, I'm doing that now
Aug 18 08:33:58 <mva> uhm... how the package containing syslogd is called? I can't see anything containing "syslog" in the gui package manager, nor apt-cache search syslog shows something relevant :-/ 
Aug 18 08:34:22 <mva> (well, maybe I've out-of-date repos list?..)
Aug 18 08:37:16 <freemangordon_> mva: sysklogd
Aug 18 08:38:13 <mva> ok, thanks
Aug 18 08:38:45 <mva> uhm...
Aug 18 08:38:51 <mva> > E: Couldn't find package sysklogd
Aug 18 08:38:53 <mva> :-/
Aug 18 08:40:58 <freemangordon_> mva: http://repository.maemo.org/pool/fremantle/free/s/sysklogd/
Aug 18 08:41:02 <freemangordon_> it is in sdk repo
Aug 18 08:51:06 <mva> freemangordon_: is it any list of "currently actual"/"musthave" repos? :)
Aug 18 09:04:08 <freemangordon_> mva: no, enable it only if needed
Aug 18 09:06:21 <freemangordon_> Wizzup: parazyd: how's amprola developing?
Aug 18 09:24:24 <Wizzup> freemangordon_: it's blocking on politics in devuan
Aug 18 09:24:37 <Wizzup> I've taken a step back and let them figure it out
Aug 18 09:29:32 <mva> btw
Aug 18 09:29:36 <mva> The following packages were automatically installed and are no longer required:
Aug 18 09:29:38 <mva>   libqt4-meegographicssystem libqt4-meegographicssystemhelper
Aug 18 09:29:46 <mva> can I safely remove them?
Aug 18 09:30:12 <mva> despite maemo is definitely not meego, package names looks dangerous to remove :-/
Aug 18 09:31:33 <Wizzup> freemangordon_: specifically, they are not in agreement on how to do the ci / trigger builds.
Aug 18 09:31:41 <Wizzup> freemangordon_: maybe something changed. parazyd knows.
Aug 18 09:37:46 <mva> anyway, here is a syslog, right from reboot: https://gist.github.com/raw/3e4007eef990f2dd8cd96e30de54cf71
Aug 18 09:55:21 <sicelo> browserd
Aug 18 10:11:42 <mva> well, it looks like it has latest version installed, so it is no way to fix it with upgrade
Aug 18 10:16:57 <mva> btw, shouldn't I ever do `apt-get dist-upgrade`? :) I do remember how it bricked my n900 once, and now it wants to: https://gist.github.com/raw/6e01f5d8f64fb7e28bc2f9b09f0e48eb
Aug 18 10:26:37 <bencoh> *never* do dist-upgrade :)
Aug 18 10:27:07 <sicelo> :-)
Aug 18 10:48:33 <freemangordon_> mva: "qtlockscreen respawning too fast..." ?!?
Aug 18 10:48:55 <mva> well, I anyway didn't agree on dist-upgrade since that time, but it is a bit important question: how to fix broswerd :-/ 
Aug 18 10:49:43 <mva> well, and qtlockscreen, yes ;)
Aug 18 10:49:51 <freemangordon_> "Process '/usr/sbin/browserd -d' with pid 1505 exited with return value 1; spawning too fast -> reset"
Aug 18 10:50:25 <freemangordon_> could you try to start it by hand from terminal, as user "user"
Aug 18 10:51:12 <mva> although, lockscreen seems to work fine (not sure if it is `qtlockscreen` or another one), but since reset comes from browserd, I guess it's important to fix it first :-/
Aug 18 10:51:49 <freemangordon_> mva: and what is qtlockscreen doint to replace tklock?
Aug 18 10:51:54 <freemangordon_> *doing
Aug 18 10:55:09 <freemangordon_> oh, it seems it does not replaces it, but puts itself on top of it. how cute
Aug 18 10:55:45 <mva> uhm...
Aug 18 10:55:49 <freemangordon_> mva: so, what is the result of executing "/usr/sbin/browserd"?
Aug 18 10:55:58 <mva> browserd started from the terminal looks working fine...
Aug 18 10:56:41 <freemangordon_> weird
Aug 18 10:58:07 <freemangordon_> hmm, wtf? "Lifeguard refused to start command (/usr/bin/ohm-session-agent) again"
Aug 18 11:00:46 <freemangordon_> mva: so, you can now browse internet?
Aug 18 11:07:21 <mva> freemangordon_: I do. Although, not that I checked it before ;)
Aug 18 11:09:07 <mva> uhm
Aug 18 11:10:32 <mva> it is no more "reset"/"exit code" in syslog, but I just found kernel traceback about wifi module :-/
Aug 18 11:11:04 <mva> well, I'll try to disable R&D mode now
Aug 18 11:11:22 <freemangordon_> mva: I have no idea why browserd is behaving, though your device seems to be with heavily modified OS
Aug 18 11:11:52 <freemangordon_> first reboot it once mor, to see if browserd stays alive after reboot
Aug 18 11:12:13 <freemangordon_> then disable r@d flags
Aug 18 11:12:14 <mva> actually, I didn't modified it more than installed some packages from extras*
Aug 18 11:12:25 <freemangordon_> ok
Aug 18 11:13:09 <freemangordon_> extras or extras-devel?
Aug 18 11:13:48 <mva> extras and extras-testing mostly
Aug 18 11:14:16 <freemangordon_> could be some package broke something
Aug 18 11:14:57 <freemangordon_> mva: also, you may want to clean microb cache to to see if it will make difference
Aug 18 11:16:06 * sicelo curses himself that he didn't use r&d mode while chasing a weird problem with unexpected reboots.  - looks like it would have nailed it right away
Aug 18 11:16:54 <mva> sicelo: not r&d as itself, but no-reboot flags, I guess :)
Aug 18 11:17:28 <sicelo> yes, of course. needs r&d, afaik
Aug 18 11:17:37 <sicelo> or not?
Aug 18 11:18:40 <mva> yup. it enabled it automatically when I set flags
Aug 18 11:23:43 <freemangordon_> Wizzup: :(
Aug 18 11:23:53 <freemangordon_> parazyd is still on holiday?
Aug 18 11:25:40 <parazyd> yeah, until september. maybe a week of september as well, depending on how my dental stuff resolves
Aug 18 11:25:49 <parazyd> but i'm around, nevertheless
Aug 18 11:26:28 <parazyd> as for devuan, there's disagreement with the ci setup/builds.. you can read about it yourself in a couple of threads on devuan-dev
Aug 18 11:26:49 <parazyd> https://lists.dyne.org/lurker/thread/20170815.083657.f9fe40bb.en.html
Aug 18 11:27:15 <parazyd> too much drama, and procrastination from certain blocking people
Aug 18 11:43:17 <mva> uhm
Aug 18 11:44:51 <mva> and should I consider moving from power-kernel to "usual" one? (not wure which package it would be right to mention: `kernel` or `kernel-maemo`) :)
Aug 18 11:44:59 <mva> s/wure/sure/
Aug 18 11:44:59 <infobot> mva meant: and should I consider moving from power-kernel to "usual" one? (not sure which package it would be right to mention: `kernel` or `kernel-maemo`) :)
Aug 18 11:54:21 <bencoh> mva: power-kernel should be fine
Aug 18 12:02:15 <Vajb> power-kernel prevents me of installing u-boot
Aug 18 12:03:16 <freemangordon_> parazyd: do I get it right that we're waiting now for the documentation of build system to be completed?
Aug 18 12:03:32 <freemangordon_> (ignoring emotions and such in those mails)
Aug 18 12:03:52 <parazyd> no, we're waiting on a decision on what gets deployed for other distros (maemo & others) to be able to build on the CI
Aug 18 12:04:19 <freemangordon_> who should decide on that and is there a deadline?
Aug 18 12:04:23 <parazyd> currently there's an existing software which certain people don't like. they promised to come up with an alternative
Aug 18 12:04:30 <freemangordon_> ah, ok
Aug 18 12:04:34 <parazyd> we gave them a deadline two weeks ago
Aug 18 12:04:44 <freemangordon_> I see
Aug 18 12:04:47 <parazyd> it wasn't done. and this didn't go through anyway. go figure
Aug 18 12:05:36 <freemangordon_> well, it is still holiday time, I would expect things to spped-up in September, lets see
Aug 18 12:05:59 <bencoh> let's say I have devuan running (on amd64), what should I do to install the hildon/maemo packages? (is there some wiki page about that?)
Aug 18 12:06:02 <parazyd> i hope so
Aug 18 12:06:29 <freemangordon_> bencoh: git clone / dpkg-buildpackage / dpkg -i
Aug 18 12:06:50 <bencoh> okay :)
Aug 18 12:07:01 <bencoh> and what if I want to build for arm ?
Aug 18 12:07:08 <freemangordon_> the same
Aug 18 12:07:46 <freemangordon_> there is no "scratchbox" for that
Aug 18 12:07:52 <bencoh> uh? they support cross-compilation out of the box with no effort?
Aug 18 12:08:05 <bencoh> (they == devuan)
Aug 18 12:08:19 <freemangordon_> they should, but I never tried it
Aug 18 12:08:25 <bencoh> hmm
Aug 18 12:08:30 <freemangordon_> however, /me gtg
Aug 18 12:08:32 <freemangordon_> bye
Aug 18 12:08:34 <bencoh> interesting
Aug 18 12:08:39 <NeKit> bencoh, or compile it on device
Aug 18 12:08:43 <bencoh> well, we'll see I guess
Aug 18 12:08:47 <bencoh> NeKit: noway! :)
Aug 18 12:09:10 <NeKit> latest Android phones do a good job on that though
Aug 18 12:09:19 <bencoh> sure but ....
Aug 18 12:09:30 <bencoh> that's useful when you're on the go
Aug 18 12:09:50 <bencoh> but it shouldn't be the main option
Aug 18 12:10:18 <bencoh> besides I don't have any for now
Aug 18 12:21:18 <Vajb> bencoh: go ahead and install devuan on n900. Can confirm that method in wiki works :)
Aug 18 12:21:36 <Vajb> I can*
Aug 18 12:21:45 <mva> btw, are there still no maemo (fremantle) repo with a fresh system software? :)
Aug 18 12:22:01 <mva> like git, rsync, busybox and so on
Aug 18 12:22:24 <mva> (and tmux, zsh, ...)
Aug 18 12:23:24 <mva> // or the only way is to prepare scratchbox and go on?..
Aug 18 12:29:34 <bencoh> mva: are you referring to the packages present in extra or to the sdk itself?
Aug 18 12:30:39 <bencoh> Vajb: won't do that on my main phone. but I have ordered a droid4 ;)
Aug 18 12:31:06 <bencoh> s/have/just/
Aug 18 12:31:06 <infobot> bencoh meant: Vajb: won't do that on my main phone. but I just ordered a droid4 ;)
Aug 18 12:32:14 <NeKit> bencoh, nice, one more Droid 4 :)
Aug 18 12:32:38 <sicelo> Vajb: which wiki?
Aug 18 12:34:16 <bencoh> I need to find a usb/serial thing now, looks like you need one to attach to serial port
Aug 18 12:36:15 <mva> bencoh: not sure, what would be the correct option to choose ;) I just want to have modern versiona of (git,rsync,busybox,tmux,zsh,vim and so on) on the n900 :)
Aug 18 12:36:40 <sicelo> bencoh: serial port on droid4?
Aug 18 12:36:41 <bencoh> mva: then sb is the way to go, yeah
Aug 18 12:36:57 <bencoh> sicelo: looks like it has something muxed on usb
Aug 18 12:37:33 <sicelo> mva: yes sb, assuming you're able to satisfy dependencies ... getting more and more diffcult
Aug 18 12:37:37 <bencoh> no idea how it works nor if it's really muxed or if there is a ftdi sitting somewhere
Aug 18 12:38:42 <Vajb> sicelo: devuan on n900 wiki. I have now 4.10.17 kernel up and running with devuan filesystem.
Aug 18 14:29:52 <mva> luke-jr: ping? have you any progress on Gentoo@N900 since the state described on wiki.m.o?
Aug 18 14:31:15 <luke-jr> no
Aug 18 14:31:20 <luke-jr> I have abandoned N900
Aug 18 14:33:29 <mva> :-/
Aug 18 14:33:39 <luke-jr> I now run Gentoo on my GPD Win
Aug 18 14:34:02 <mva> so, they doesn't locked bootloader? :)
Aug 18 14:34:09 <mva> nice
Aug 18 14:34:41 <mva> // I just periodically looking on their ubuntu version problems, lol
Aug 18 14:35:32 <luke-jr> dunno, I downgraded the BIOS
Aug 18 14:52:42 <Wizzup> mva: I have gentoo on my n900 with mainline kernel
Aug 18 14:52:55 <Wizzup> can't say gentoo is ideally suited for it though 
Aug 18 14:53:27 <Wizzup> freemangordon: btw I think the devuan situation will resolve itself soonish, at least .. I hope
Aug 18 14:53:42 <Wizzup> I don't plan to block on it anyway
Aug 18 15:02:07 <bencoh> luke-jr: gpdwin looks nice but it has no modem :(
Aug 18 15:02:19 <luke-jr> bencoh: tethering works ;)
Aug 18 15:02:37 <luke-jr> bencoh: you could also look at Pyra, but it's much more $ and still not shipping
Aug 18 15:02:59 <luke-jr> https://www.pyra-handheld.com/wiki/index.php?title=Comparison_Chart
Aug 18 15:03:56 <bencoh> luke-jr: I gave up on pyra
Aug 18 15:05:58 <luke-jr> I'm tempted to
Aug 18 15:06:05 <luke-jr> GPD Win is probably good enough
Aug 18 15:06:11 <luke-jr> and much more powerful
Aug 18 15:06:20 <luke-jr> not to mention can run with free software
Aug 18 17:21:36 <DocScrutinizer05> hey folks, can I call normal cli commands from php scripts?
Aug 18 17:21:58 <DocScrutinizer05> e.g. sleep 10
Aug 18 17:22:17 <DocScrutinizer05> or logger
Aug 18 17:23:43 <KotCzarny> system("command1; command 2; etc;");
Aug 18 17:23:56 <DocScrutinizer05> ta
Aug 18 17:24:21 <KotCzarny> some hostings block those though, then you have to use popen() etc
Aug 18 17:24:30 <DocScrutinizer05> eeew
Aug 18 17:24:52 <DocScrutinizer05> fsck oho
Aug 18 17:24:58 <DocScrutinizer05> php even
Aug 18 17:49:55 <DocScrutinizer05> hmm, system("logger -t subscribe.php $_POST['foo-mail']"); fails
Aug 18 17:51:16 <KotCzarny> you have to use ${varial
Aug 18 17:51:20 <KotCzarny> you have to use ${variable[]}
Aug 18 17:51:23 <KotCzarny> when inside ""
Aug 18 17:51:36 <KotCzarny> or "...".$variable[]."..."
Aug 18 17:51:46 <KotCzarny> and mind the fullpaths
Aug 18 18:01:26 <DocScrutinizer05> ta, works
Aug 18 18:06:55 <DocScrutinizer05> now for some skiddie blocker in that shite
Aug 18 18:20:43 <DocScrutinizer05> and prolly best reject gmail addr right away
Aug 18 18:22:08 <DocScrutinizer05> I get each root mail triple, for redundancy. And each gmail newsletter abo sends ~7 info mails about "still tryong..." and finally "returned to sender..."
Aug 18 18:22:43 <DocScrutinizer05> while I guess many abos are just by skiddies
Aug 18 18:25:50 <KotCzarny> throw in display resolution nearby
Aug 18 18:25:54 <KotCzarny> erm. wrong chan
Aug 18 21:28:53 <Maxdamantus> ...".escapeshellarg($_POST['foo-mail'])."...
Aug 18 21:29:33 <Maxdamantus> Though it would preferably just not go through the shell, so you'd just specify the arguments as an array.
Aug 18 21:35:50 <Maxdamantus> also, if escapeshellarg is used there, it should also have "--" as an argument before the email.
Aug 18 21:38:35 <Maxdamantus> Could probably otherwise do some sort of DoS using foo-mail=-f/dev/urandom
**** ENDING LOGGING AT Sat Aug 19 03:00:00 2017