2017-01-20

Slitaz -- UUID="2017-01-19-08-32-05-00" LABEL="SliTaz preinit"


UUID="2017-01-19-08-32-05-00" LABEL="SliTaz preinit"

slitaz64:
No kernel modules.

2017-01-16

Slitaz64 -- UUID="2017-01-15-02-37-20-00" LABEL="SliTaz core64" -2



Distro: rolling-core64
http://cook.slitaz.org/cookiso.cgi?distro=rolling-core64

Installing package: linux64-wireless Unable to find package "linux64-cryptolinux-libre-crypto" in the mirrored packages list.
Unable to find package "get-linux64-cryptolinux-libre-crypto" in the mirrored packages list. [ Done ]

Installing package: firmware-rt2x00 Unable to find package "linux64-wirelesslinux-libre-wireless" in the mirrored packages list.
Unable to find package "get-linux64-wirelesslinux-libre-wireless" in the mirrored packages list. [ Done ]
Installing package: firmware-rtlwifi Unable to find package "linux64-wirelesslinux-libre-wireless" in the mirrored packages list.
Unable to find package "get-linux64-wirelesslinux-libre-wireless" in the mirrored packages list. [ Done ]

Installing package: locale-it Checksum error for "locale-it-5.0.tazpkg" [ Done ]

Installing package: xorg-server Unable to find package "linux64-drmlinux-libre-drm" in the mirrored packages list.
Unable to find package "get-linux64-drmlinux-libre-drm" in the mirrored packages list. [ Done ]

Installing package: yad Checksum error for "yad-gtk3-0.28.1.tazpkg" [ Done ]


Distro statistics: /home/slitaz/distro
================================================================================
Build time : 842s ~ 14m
Build date : 20170115
Packages : 288
Rootfs size : 184.6M
Initramfs size : 45.3M
ISO image size : 50.0M
================================================================================
Image is ready: slitaz-core64.iso

Moving ISO to: /home/slitaz/iso/slitaz-rolling-core64.iso
Cookiso ended: 2017-01-15 02:37

Slitaz64 -- UUID="2017-01-15-02-37-20-00" LABEL="SliTaz core64"




ifconfig: SIOCGIFFLAGS: No such device

tux@slitaz:~$ grep -A5 network /var/log/boot.log
Processing: /etc/init.d/network.sh
Loading network settings from /etc/network.conf
Setting hostname to: slitaz [ Done ]
Configuring loopback... [ Done ]
ifconfig: SIOCGIFFLAGS: No such device
Starting udhcpc client on: eth0...
udhcpc: SIOCGIFINDEX: No such device

tux@slitaz:~$ lsmod
Module Size Used by Not tainted

tux@slitaz:~$ blkid
/dev/sr0: UUID="2017-01-15-02-37-20-00" LABEL="SliTaz core64" TYPE="iso9660" PTUUID="587ad259" PTTYPE="dos"

2017-01-05

Slitaz64 -- Stack Protector buffer overflow detection


Stack Protector buffer overflow detection

Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
Makefile:1066: recipe for target 'prepare-compiler-check' failed

root@slitaz:/usr/src/linux-4.9# grep STACKPROTECTOR .config
CONFIG_HAVE_CC_STACKPROTECTOR=y
CONFIG_CC_STACKPROTECTOR=y
# CONFIG_CC_STACKPROTECTOR_NONE is not set
# CONFIG_CC_STACKPROTECTOR_REGULAR is not set
CONFIG_CC_STACKPROTECTOR_STRONG=y


Stack Protector buffer overflow detection

This option turns on the "stack-protector" GCC feature. This
feature puts, at the beginning of functions, a canary value on
the stack just before the return address, and validates
the value just before actually returning. Stack based buffer
overflows (that need to overwrite this return address) now also
overwrite the canary, which gets detected and the attack is then
neutralized via a kernel panic.

Prompt: Stack Protector buffer overflow detection
Location:
-> General setup
Defined at arch/Kconfig:417
Depends on: HAVE_CC_STACKPROTECTOR [=y]
Selected by: HAVE_CC_STACKPROTECTOR [=y] && m

Strong (CC_STACKPROTECTOR_STRONG)

CONFIG_CC_STACKPROTECTOR_STRONG:

Functions will have the stack-protector canary logic added in any
of the following conditions:

- local variable's address used as part of the right hand side of an
assignment or function argument
- local variable is an array (or union containing an array),
regardless of array type or length
- uses register local variables

This feature requires gcc version 4.9 or above, or a distribution
gcc with the feature backported ("-fstack-protector-strong").


On an x86 "defconfig" build, this feature adds canary checks to
about 20% of all kernel functions, which increases the kernel code
size by about 2%.

Symbol: CC_STACKPROTECTOR_STRONG [=n]
Type : boolean
Prompt: Strong
Location:
-> General setup
-> Stack Protector buffer overflow detection ( [=y])
Defined at arch/Kconfig:449
Depends on:
Selects: CC_STACKPROTECTOR [=y]

Regular (CC_STACKPROTECTOR_REGULAR)

CONFIG_CC_STACKPROTECTOR_REGULAR:


Functions will have the stack-protector canary logic added if they
have an 8-byte or larger character array on the stack.

This feature requires gcc version 4.2 or above, or a distribution
gcc with the feature backported ("-fstack-protector").


On an x86 "defconfig" build, this feature adds canary checks to
about 3% of all kernel functions, which increases kernel code size
by about 0.3%.

Symbol: CC_STACKPROTECTOR_REGULAR [=n]
Type : boolean
Prompt: Regular
Location:
-> General setup
-> Stack Protector buffer overflow detection ( [=y])
Defined at arch/Kconfig:435
Depends on:
Selects: CC_STACKPROTECTOR [=y]

Slitaz -- LINUX_VERSION_CODE / dec2hex / hex2dec



LINUX_VERSION_CODE / dec2hex / hex2dec


tux@slitaz:~$ cat /usr/src/linux-3.16.36/include/generated/uapi/linux/version.h

#define LINUX_VERSION_CODE 200740

#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))


dec2hex / hex2dec

tux@slitaz:~$ printf "%X\n" 200740

31024


tux@slitaz:~$ echo $((0x31024))

200740

tux@slitaz:~$


31024 ⇒ 3.10.24 (hex) ⇒ 3.16.36