The previous chapters covered SELinux, which is the default Mandatory Access Control (MAC) system on RHEL-family distributions. This chapter introduces AppArmor, which is the default MAC system on Ubuntu and SUSE. Both systems enforce a security policy that sits behind the traditional Unix permissions, but they use fundamentally different models. SELinux uses inode-based labels and…
The previous chapters covered the SELinux modes, contexts, and booleans. This chapter covers the workflow for diagnosing an access denial. An application fails, the logs show a denial, and the administrator must decide whether the cause is a mislabeled file, a boolean that needs to be toggled, a port that is not permitted, or a…
The previous chapter covered security contexts and labels: the data that the SELinux policy uses to identify files and processes. This chapter covers the switches that adjust the policy without recompiling it. A SELinux boolean is a named toggle that the policy checks at runtime. When the toggle is on, a specific rule or set…
The previous chapter introduced the SELinux modes: Enforcing, Permissive, and Disabled. This chapter covers the data that the policy actually evaluates: the security context. Every process, file, directory, and socket in a SELinux system carries a label, and the policy rules match on the type field of that label, not on the file path or…
The previous chapter covered the route tree and its type generation. This chapter covers the component that the user actually clicks to move between routes: the <Link> component. It is the TanStack Router equivalent of React Router’s <Link>, but the type safety is stricter. The to prop is not a generic string. It is a…
The previous chapter covered the file conventions that map a directory structure to URLs. This chapter covers the route tree itself: the nested data structure that the router uses to match URLs and the generated types that make navigation type-safe. A route tree is not a flat list. It is a hierarchy of routes, where…
The previous chapter created the root route and the layout. This chapter covers the file-based routing convention: the directory structure under src/routes/, the file naming rules that map a file to a URL, and the generated routeTree.gen.ts that connects the files to the router. The LFCS exam does not test TanStack Router, but the front-end…
The previous chapter installed TanStack Router and configured the Vite plugin. This chapter covers the root route, which is the foundation of the entire route tree. Every application has exactly one root route, created with createRootRoute or createRootRouteWithContext. The root route defines the layout that wraps every other route: the navigation header, the footer, the…
TanStack Router is a type-safe routing library for React and Solid. Unlike React Router, which relies on runtime matching, TanStack Router generates a fully typed route tree that the TypeScript compiler can verify. The installation process is split into two paths: the CLI scaffold for new projects, and the manual setup for existing projects. The…
The previous chapter covered the fallback route for unmatched URLs. This chapter covers the mechanism that users actually click to move between routes: the <Link>, <NavLink>, and <Navigate> components. A plain HTML <a href=”…”> triggers a full page reload. The browser sends a new HTTP request, the server returns a new HTML document, and the…