Enablers, head spaces and physical spaces for issues and more general troubleshooting


#41

MAC addresses really wont aide anyone in ‘hacking’ you. They arent useful through a layer3 device, so as for the greater internet goes… there’s no point. Sure someone could clone their local MAC to be the same as yours, but that’s not going to help in hacking you. They’d have to be on your local network to get any benefit out of knowing your MAC, like with an ARP Poisoning attack. If they were already on your local network, getting your MAC is simple.

Also dont ever trust anything online that claims to ‘self destruct’. Just because you ‘see’ the data after x days or other period of time does not mean that the data is not still there. And it does nothing for people who have saved a local copy. If you don’t want nefarious people to see it… dont ever post it on the internet.

I understand the desire for information security, but having worked in that exact industry for well over 15 years… the truth is that if someone is determined there isn’t any information security you can rely on. And if your basis for feeling secure is obscurity… just quit now.

You leak more about yourself through random things online than you ever will through an about screen. You think you Glendale will get the rain they are predicting for Monday? Other than that, it looks like you will have a nice week of weather.


#42

I understand your point, but I’m not intending to stop state actors or anything, primarily the point of my actions is to halt scripts and general criminal actors, as opposed to targeted attacks against me directly.


#43

I didn’t mean to imply State Actors, but I understand where you’re coming from now. If you’re only worried about general cyber crime, then let out a sigh of relief. People who are in cyber crime are in it for easy money. There is no easy money in trying to ‘hack’ FreeBSD systems; when, with simple malware, you can pop thousands of Windows machines per day. Putting out the effort and resources to not only discover but then exploit 0-Days on FreeBSD is counter productive to their goals.
Linux will get targeted long before cyber criminals start trying to attack BSD based systems. With IPFW running by default (as TrueOS does), you’re more than secure. You could let them know the entire configuration of your system, and it’d do them no good. I’m not saying FreeBSD systems can’t be hacked, I’m saying none of us are that important or worth enough for any cyber crime syndicate to bother.

As for scripts… Even if you manually downlaoded one… it wouldnt be able to run on your system unless you manually chmod it, and then manually launch it., so there’s little to worry about in that regard. But we’re quickly sliding off topic… if you’d like to discuss TrueOS security, start up another thread. I’m sure there are others that would join in as well. :slight_smile:


#44

Examples:

$ ./about

===================
General information
===================

boot environment now (N) … 12.0-CURRENT-up-20170211_154130 N 2017-02-11
       after restart (R) … 12.0-CURRENT-up-20170214_185715 R 2017-02-14
boot loader …………………………………… BSD
            type ……………………… EFI
CPU ………………………………………………………… Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
    number of cores ……………… 2
host ……………………………………………………… momh167-gjp4-hpelitebook850g2-trueos.university.brighton.ac.uk
memory ………………………………………………… 16384 MB available, 4117 MB free
OS git branch ……………………………………………………………………………………… drm-next
OS git revision ………………………………………………………………………………… cea905a
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… CUSTOM
TrueOS version …………………………… TrueOS-Desktop-201702011813
uptime ………………………………………………… 9:01
user  …………………………………………………… grahamperrin

More (TrueOS Desktop):

    desktop environment …… KDE
    sound card driver ………… pcm1: <Realtek (0x0280) (Analog 2.0+HP/2.0)> on hdaa1  (1p:1v/1r:1v) default
    wireless driver ……………… iwm0
    X11 drivers ………………………… modesetting_drv.so 

$ 

-v for verbose is not yet implemented:

$ ./about -v
-a show all information
-n show network information only
$ 
$ ./about -a

===================
General information
===================

boot environment now (N) … 12.0-CURRENT-up-20170211_154130 N 2017-02-11
       after restart (R) … 12.0-CURRENT-up-20170214_185715 R 2017-02-14
boot loader …………………………………… BSD
            type ……………………… EFI
CPU ………………………………………………………… Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
    number of cores ……………… 2
host ……………………………………………………… momh167-gjp4-hpelitebook850g2-trueos.university.brighton.ac.uk
memory ………………………………………………… 16384 MB available, 4110 MB free
OS git branch ……………………………………………………………………………………… drm-next
OS git revision ………………………………………………………………………………… cea905a
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 12.0-CURRENT
OS version and patch level …… (freebsd-version) 12.0-CURRENT
TrueOS package set ………………… CUSTOM
TrueOS version …………………………… TrueOS-Desktop-201702011813
uptime ………………………………………………… 9:02
user  …………………………………………………… grahamperrin

More (TrueOS Desktop):

    desktop environment …… KDE
    sound card driver ………… pcm1: <Realtek (0x0280) (Analog 2.0+HP/2.0)> on hdaa1  (1p:1v/1r:1v) default
    wireless driver ……………… iwm0
    X11 drivers ………………………… modesetting_drv.so 


==========
Networking
==========

Default routing table
---------------------

   route to: default
destination: default
       mask: default
    gateway: 192.168.1.1
        fib: 0
  interface: wlan0
      flags: <UP,GATEWAY,DONE,STATIC>
 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1500         1         0 

Routing table in numeric format
-------------------------------

Routing tables

Internet:
Destination        Gateway            Flags     Netif Expire
default            192.168.1.1        UGS       wlan0
127.0.0.1          link#2             UH          lo0
192.168.1.0/24     link#3             U         wlan0
192.168.1.7        link#3             UHS         lo0
193.62.168.0/24    link#1             U           em0

Internet6:
Destination                       Gateway                       Flags     Netif Expire
::/96                             ::1                           UGRS        lo0
::1                               link#2                        UH          lo0
::ffff:0.0.0.0/96                 ::1                           UGRS        lo0
fe80::/10                         ::1                           UGRS        lo0
fe80::%em0/64                     link#1                        U           em0
fe80::5a20:b1ff:fed8:f966%em0     link#1                        UHS         lo0
fe80::%lo0/64                     link#2                        U           lo0
fe80::1%lo0                       link#2                        UHS         lo0
ff02::/16                         ::1                           UGRS        lo0

Interface information, condensed
--------------------------------

em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=53d9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO>
        inet6 fe80::5a20:b1ff:fed8:f966%em0 prefixlen 64 scopeid 0x1 
        inet 193.62.168.100 netmask 0xffffff00 broadcast 193.62.168.255 
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo 
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255 
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11a
        status: associated
        regdomain FCC country US authmode WPA2/802.11i privacy ON
        deftxkey UNDEF TKIP 2:128-bit txpower 17 bmiss 10 mcastrate 6
        mgmtrate 6 scanvalid 60 wme roaming MANUAL
        groups: wlan 

DNS-related
-----------

;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 10119
;; flags: qr rd ra ; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 15 
;; QUESTION SECTION:
;; .    IN      NS

;; ANSWER SECTION:
.       16200   IN      NS      d.root-servers.net.
.       16200   IN      NS      e.root-servers.net.
.       16200   IN      NS      f.root-servers.net.
.       16200   IN      NS      g.root-servers.net.
.       16200   IN      NS      h.root-servers.net.
.       16200   IN      NS      i.root-servers.net.
.       16200   IN      NS      j.root-servers.net.
.       16200   IN      NS      k.root-servers.net.
.       16200   IN      NS      l.root-servers.net.
.       16200   IN      NS      m.root-servers.net.
.       16200   IN      NS      a.root-servers.net.
.       16200   IN      NS      b.root-servers.net.
.       16200   IN      NS      c.root-servers.net.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:
a.root-servers.net.     3589404 IN      A       198.41.0.4
b.root-servers.net.     3589404 IN      A       192.228.79.201
c.root-servers.net.     3588257 IN      A       192.33.4.12
d.root-servers.net.     3588256 IN      A       199.7.91.13
e.root-servers.net.     3588256 IN      A       192.203.230.10
f.root-servers.net.     3588256 IN      A       192.5.5.241
g.root-servers.net.     3588256 IN      A       192.112.36.4
h.root-servers.net.     3588257 IN      A       198.97.190.53
i.root-servers.net.     3588256 IN      A       192.36.148.17
j.root-servers.net.     3588256 IN      A       192.58.128.30
k.root-servers.net.     3588256 IN      A       193.0.14.129
l.root-servers.net.     3588256 IN      A       199.7.83.42
m.root-servers.net.     3588256 IN      A       202.12.27.33
a.root-servers.net.     3559678 IN      AAAA    2001:503:ba3e::2:30
b.root-servers.net.     3559678 IN      AAAA    2001:500:84::b

;; Query time: 2 msec
;; SERVER: 192.168.1.1
;; WHEN: Thu Feb 16 06:50:11 2017
;; MSG SIZE  rcvd: 492

----

IPv4 key points (not interface specific): 

    193.62.168.100
    127.0.0.1
    192.168.1.7

IPv6 key points (not interface-specific): 

    fe80::5a20:b1ff:fed8:f966%em0
    ::1
    fe80::1%lo0

$ 

#45

about

boot environment now (N) … 
       after restart (R) …
… 
TrueOS package set …

In some cases the package set in output from about is not the set that produced the current boot environment. This can happen when, for example, a repository preference is changed after boot.

In other cases, neither of the listed boot environments will relate to the listed package set.

Ideally there should be a method to easily determine whether a boot environment was the product of a stable, unstable or custom repository.

Realistically – less methodically – it may help to include some update-related information in output from about. I’ll give it thought over the weekend.


#46