All Projects

This addon works for any firefox based browser but not seamonkey based or this.

I wondered if you could implement the iceweasel one for Iceape.

sslsleuth

http://repository.binaryoutcast.com/artifacts/navigator-builds/

http://binaryoutcast.com/projects/borealis/

unlike Navigator though, it needs two things: compatibility with seamonkey addons, (the ones that effect web browsing, not the mail email parts)

and to be based off of the latest version of seamonkey, only obviously just the navigator part. I understand this might be hard to implement now, so I can wait if need be, Just thought I would show this to you.

PS, if you ever make HyperBK, port it to that too, but until then, just the os that I mentioned.

Also, last thing, any seamonkey addons that I have already asked for seamonkey, again that aren’t email/mail based, implement them for this too. :)

I will put the severity at very low if that’s okay, just until you have actual time/whatever...

Let me know if this is even remotely possible with this build.

https://github.com/loh-tar/wpa-cute/releases

I know there are plans to remove NetworkManager. I wondered if we could replace it in 0.4 with Wpa_Cute. seen in the above link.

I haven’t been able to compile it, but it has been updated as recent as 2018 december (stable)

or 2019 january. :)

WPA_GUI doesn’t seem to work well for me, it runs into weird errors when I start it. Long story short, I run into this issue with wpa_supplicant when i do it manually:

https://wiki.archlinux.org/index.php/Wpa_supplicant:

Password-related problems

wpa_supplicant may not work properly if directly passed via stdin particularly long or complex passphrases which include special characters. This may lead to errors such as failed 4-way WPA handshake, PSK may be wrong when launching wpa_supplicant.

In order to solve this try using here strings wpa_passphrase <MYSSID> «< “<passphrase>” or passing a file to the -c flag instead:

# wpa_supplicant -i <interface> -c /etc/wpa_supplicant/example.conf

In some instances it was found that storing the passphrase cleartext in the psk key of the wpa_supplicant.conf network block gave positive results (see [2]). However, this approach is rather insecure. Using wpa_cli to create this file instead of manually writing it gives the best results most of the time and therefore is the recommended way to proceed.
Problems with eduroam and other MSCHAPv2 connections

This is my issue with wpa_supplicant sadly... and I do not know how to workaround that without a GUI.

but Wpa_Supplicant_gui does not fix it either, it doesn’t even load properly on my other laptop.

It says it cannot get the status of wpa_supplicant when I load it.

This could be an issue if you get rid of NetworkManager for some users.

So yeah, please take a look at my request okay? Wait for 0.3 to be released to add this if possible. I know you guys are overworked, etc... and it doesn’t need to be done now anyhow. ;)

from the, forums I have heard you plan to base your new iceweasel version from basilisk when firefox switches to web extensions completely. I am concerned about this because noscript and many other addons will no longer support legacy after this point...

I really think you are doing a disservice if you do this. I think we should personally fix the leaks that mozilla makes, the way trisquel 8 does it. I have heard they know how to fix those leaks. Or, another way forward would be to find a way that involves forking firefox esr 60 and correcting the bugs with the help of tcpdump.

Its madness to fork from basilisk because without noscript webextensions and other such addons, any benefits you get will be very small compared to what you have lost in the process.

I doubt you want to have two different versions of iceweasel esr, one that is with webext and one without. But please don’t try to use basilisk as the base for iceweasel.

I really think its a bad idea long term. Do I dislike mozilla’s new plan? Yes... of course. But do I think using basilisk will solve it? Not unless mozilla angers enough people to make their addons for basilisk instead... Which I really, really doubt very highly.

Please hear this request and don’t just close it. Rather, instead discuss it for a long time. Without noscript, firefox is immensely insecure. And Firefox’s legacy noscript version will die in the future. In the NEAR FUTURE I MIGHT ADD

Of course, there are other firefox addons I want that are webext. So yeah... Nano Adblocker, Privacy Settings, Privacy Possum/Privacy Badger, Viewtube, Decentraleyes to name a few.

I would like it if you could, fork noscript legacy and constantly update it based on the webext one’s changes without of course, using the webext.

What I mean, is be applying the new security fixes they put into the webext one (the ones you need)

and then, apply them into iceweasel-classic’s noscript.

Even if you plan on updating it once a month, this is critical in my opinion for keeping the browser safe.

5.1.85 is the current latest legacy noscript version within noscript.net’s website.

ps, this is doable right?

We don’t want obsolete software after all.

would it be possible to make it use sudo instead?

From what I know, sudo is safer. Let me know if you agree this is a problem.

No root settings found in /etc/spacefm/ Setting a root editor in Preferences should remove this warning on startup. Otherwise commands run as root may present a security risk.
EXEC(/usr/share/applications/sakura.desktop)=sakura

I am not sure how much of a risk this is, I will set it at high for now, but feel free to change it to low if its not a huge issue.

Cannot mix incompatible Qt library (version 0×50800) with this library (version 0×50904)
Aborted

./Nextcloud-2.3.3-x86_64.AppImage: /usr/lib/libQt5Core.so.5: version `Qt_5.9’ not found (required by /tmp/.mount_NextclpprMnG/usr/bin/../lib/libqt5keychain.so.1

These two packages are directly affected by an older qt5...

Could you update all the qt packages to the LTS version available?

There appears to be a bug with the current version of ufw, 0.35-2

Dunno if updating it would fix it, but it is kind of annoying and possibly security issue.

it says ufw is inactive when I reboot despite it being installed in the runlevel.

We seem to have a very old version of xscreensaver... Could you possibly update it?

this may be a security issue/privacy issue.

The useragents in random agent spoofer are detected as old apart from, firefox 60 for win7 and win10.*

I recommend focusing on the ones most people still use of each os type and scrapping the rest.

aka, for each section, such as winbugs, mac, gnu/linux... unix, android, etc...

Keep the most used ones, and update them often.

I only suggest this, because it is less work for your team.

*Of all the firefox ones, those are the only ones that work...

Add version 5.1.9

Very important for iceape users to keep updated often.