meta user
network profile
| bio | website | |
|---|---|---|
| location | United States | |
| age | ||
| visits | member for | 1 year, 10 months |
| seen | 10 hours ago | |
| stats | profile views | 85 |
|
Mar 20 |
comment |
Linux utility to monitor for stupid / likely ill-advised commands @RobM, the validation would not modify any command - it would just run up against a dictionary of known potential issues and solutions, and kindly suggest to the admin not to go through with it. As far as bugs in the validation, applying regex should be fairly straightforward and there are many proven tools. I see what you are saying about over-reliance, but the same rules still apply - if you were really concerned about it, you could email all of the instances where it threw a concern to a superior so that he could see what's going on. I'm just a bit surprised this doesn't already exist... |
|
Mar 20 |
comment |
Linux utility to monitor for stupid / likely ill-advised commands Wouldn't you agree though that the probability that anybody - regardless of skill level - would have intended to use such commands is pretty low? And since it's only interactive sessions (ie relatively few commands, not bash scripts or whatnot), what would be the harm in just running it by some regex validation? If you're logged in as root, chmod 755 etc and chmod 755 /etc are a paltry character away, and it takes so little resources to check for these things... |
|
Mar 20 |
revised |
Linux utility to monitor for stupid / likely ill-advised commands edited body |
|
Mar 20 |
asked | Linux utility to monitor for stupid / likely ill-advised commands |
|
Mar 20 |
accepted | Implementing a form of port knocking + Phone Factor = 2 Factor auth for RDP? |
|
Mar 20 |
comment |
pfsense: all interfaces up, but all non default gateways down The "network view" thing makes a lot more sense to me heuristically - thanks for the info. |
|
Mar 20 |
comment |
pfsense: all interfaces up, but all non default gateways down @ChrisS, meaning is all traffic still just going to the default gateway, and then the floating firewall rule is applied there to forward along to another interface? ... and can you think of any reason why I was able to ping 8.8.8.8 despite the fact that the rule was being applied? |
|
Mar 20 |
accepted | pfsense: all interfaces up, but all non default gateways down |
|
Mar 20 |
answered | pfsense: all interfaces up, but all non default gateways down |
|
Mar 20 |
comment |
Using DHCP with Multi-Homed NICs I have read that this may impact the use of high availability features in VMWare, but I can't remember why that was the case. Maybe I am confusing the issue with something else. |
|
Mar 17 |
asked | pfsense: all interfaces up, but all non default gateways down |
|
Mar 15 |
awarded | Popular Question |
|
Mar 14 |
accepted | Constantly having to net stop start dnscache after adding new entries in dns |
|
Mar 14 |
comment |
Can VPNs reduce latency? Assuming traffic is routed the same, the non-VPN latency is a lower bound. VPN can (at best) do epsilon worse. |
|
Mar 14 |
comment |
VMware ESX/i syslog content @MHibbin, +1 yes, in the future I should probably read before I comment. |
|
Mar 14 |
comment |
IPSec L2L Failover between two pfSense devices Also, can you elaborate a little bit on the OpenVPN + a routing protocol route? I would expect you use the "any" interface, but then how does the routing protocol factor in? |
|
Mar 14 |
comment |
IPSec L2L Failover between two pfSense devices Is 2.1 considered safe to use for a branch office? (I realize this is kind of a loaded/stupid question.) |
|
Mar 14 |
revised |
IPSec L2L Failover between two pfSense devices added 40 characters in body |
|
Mar 14 |
asked | IPSec L2L Failover between two pfSense devices |
|
Mar 14 |
accepted | pfSense to ASA L2L VPN - infrequent, short-lasting, but consistent disconnections |
