About

There is a wip dissector for the windows search protocol from gregor beck, I have used it, it's nice but it is missing some things I need. I have no idea about wireshark dissectors, I would like to hack on this and make it more useful to me,

I have no one vision of a project just some mish-mash random things I would like to explore for some hacking fun + would like to continue previous work from hackweek11 on the Windows Protocol dissector, some messages are still incomplete, also there are some known bugs (well at least I know about them) that I would like to address

Windows Search Protocol

Due to the day to day grind I have had no chance in the last months to play more with the Windows Search Protocol, however there are a number of things that I need to do to improve

Quota support

There already exists some quota support for samba both on client side and server side.

python yast

My colleague David Mulder started a new version of python yast bindings, I've started to use it for some samba related stuff. However my python is poor, my yast UI knowledge is even poorer :-) I'd like to rewrite the ruby yast examples in python, that way I can hopefully learn a bit more about

I use vim (yes one of those people) but I am a real non power user, I'd like something like Aurelien's smbmode for Emacs to be available when I open samba log files in vim. I have no idea how possible or not this is. I came across this tutorial/book some time ago but didn't find the time to look at it. I'd like to go through the book and hopefully have a crack at starting a samba log reader plugin for vim (duplicating the features from smbmode)

Samba now has an experimental Spotlight backend using Elasticsearch as fileindex. It seems that creating a similar backend could also be something that could be useful to investigate in the context of the windowssearch feature for samba

Project Description

Continuation of exploration of using elasticsearch to provide windows search functionality with samba

Project Description

Recently got a (simple) solar system installed, however the useful data is available from multiple sources each of which doesn't really tell me (easily) what is going on at all times

Project Description

Last hackweek I worked on a solar monitor for our solar installation detail are here. At the time I didn't have a device to load it on but eventually I got a hold of a raspberry pi (and screen). I ended up building yast for it and got it working. Unfortunately I couldn't get the touch screen to work for it with tumbleweed on pi so I ended up using the debian based raspberry pi OS. This works pretty well except for an annoying wrinkle, it seems a long running yast (using our yast python bindings) ui app burns memory and it ends freezing the raspberry pi nearly once a day so now I have a cron job to kill the X server twice a day (just to be sure) so that the monitor UI is restarted. This is probably the most serious issue (and really I suppose needs attention as it affects anything else using the yast python bindings). There are other issues (and bugs) with the solar monitor that I haven't had a chance to investigate that I would love to work on over hack week