Packages update Request
-
HI I know that everyone has given a lot to the development of pfsense and i thank you for all the time and effort that you have given in making pfsense, I can't thank you guys enough.
But I was wondering if someone can update these packages to
Nmap 5.00
squid-3.0
SquidGuard-1.4
Havp Version 0.91
imspector-0.9
Thank you
-
I'm have rest. Maibe return to the packages at september.
-
Hey,
Any progress on this avserg?
imspector would be useful, since the group-chat issue with the new MSN version is resolved in 0.9.
Or is there a way to manually upgrade imspector that would work?
-
I believe dsverg was commenting on the squidguard package and not any others.
billm did a lot of work on the IMspector package. If you want it updated, I would suggest starting a bounty and he might find the time to work on it again. -
There is a bounty started on updating squid. If others would help contribute to the bounty, it might get the interest of a developer.
-
Sorry guys, I was busy in September. How to appear a little free time - I'll do anything. :-\
-
Sorry guys, I was busy in September. How to appear a little free time - I'll do anything. :-\
dvserg,
Thanks for all the great work you've done. I updated the squid and squidguard package to work properly on NanoBSD – Namely adding conf_mount_rw(); and conf_mount_ro(); calls around where disk writes were needed, making sure file downloads go to /root and not /tmp (since /tmp is very small on NanoBSD), and so on. I have not been able to get to the HAVP package, however. I'm not sure what changes may need to be made in order to make it work there, since the RAM and writable space are limited it may not work at all. You can review my commits to the package repository over the past week and see what I have done.
If you could take a look at the HAVP package code and see if you can come up with a way to make that work it would be appreciated. I suppose forcing a RAM disk for scanning would be ideal, but that would also limit the file scan size a bit. Probably a good idea to limit it anyhow, since the resources are limited in general when dealing with embedded systems.
Feel free to say "sorry, I don't think it will work" also, that's a valid choice, but we'd like to open as many packages up for NanoBSD as possible.
Thanks!
-
I believe dsverg was commenting on the squidguard package and not any others.
billm did a lot of work on the IMspector package. If you want it updated, I would suggest starting a bounty and he might find the time to work on it again.I'm kinda new to this forum, so pardon my stupid questions. How to start a bounty?
-
Under Post a Bounty.
-
No news on havp/embedded, I take it? I really like having the nanobsd setup, but I may have to switch back to the HD install I was using, since I am not wild about having no antivirus setup.
-
Just noticed the nano platform now has a dashboard widget for havp? Does this mean havp is being worked on? If not, I'm not sure what the point is?
-
I just forgot to tag the havp widget as not being for embedded, but I would like to see havp working on nanobsd if possible. I haven't had any more time to look at it.
-
bummer, i had high hopes :) Is there any way I can help with this? I work with software for a living, so I'm not out of my depth here…
-
I outlined what needs to happen a few posts back when I addressed a post toward dvserg. Basically any time that the package needs to write to the CF, it needs to first switch to read/write mode and then back to read only mode when complete. This would be for config changes, writing out an RC script, updating virus defs, etc.
Also, HDD scanning would have to be disabled, and only RAM disk scanning allowed, since there is no HDD. (Eventually I suppose support could be added to allow using external storage such as a USB HDD, but that is beyond the scope of what we're doing right now)
File activity in /tmp and /var need to be limited as well. You can write small files there all the time but nothing large, as it is also a RAM-based disk.
-
Okay, this sounds manageable, given that I am on a learning curve here (bsd pkg system). Would I take the HD version of the package and make those changes? If so, where would I get it?
-
It's not the bsd package system you'd be dealing with, but the pfSense package system.
You can checkout the pfSense packages repo from git if you want to look at the individual packages.
-
sorry for the confusion. i'm aware there is a difference - i was referring to the pkg_* system, which is specific to BSD, not (for example) linux. i will take a look…
-
Ah… well, the pfSense package stuff is mainly XML and PHP. In this case, all of the changes will probably be in the PHP code for the package.
-
I am not clear if there is a difference between the embedded versions and the full versions, in terms of: are there different actual packages, or does the package have to figure out the operating environment and act accordingly?
-
There is no difference in packages. If any platform-specific code is needed, you can check /etc/platform, if the file contains the text "nanobsd" then it's on nanobsd.
The functions to mount things read/write and read only are basically a no-op on full installs, so they can be inserted where needed and will only affect nanobsd.
