FAQ#16 - add link
Hi, please check my diff for www part of cvs (faq16.html). ok? BR Oleg Pahl Index: faq/faq16.html === RCS file: /cvs/www/faq/faq16.html,v retrieving revision 1.13 diff -u -p -u -p -r1.13 faq16.html --- faq/faq16.html 21 Jan 2019 02:29:34 - 1.13 +++ faq/faq16.html 28 Mar 2019 10:10:18 - @@ -290,7 +290,7 @@ This option only works for Ethernet-base prevents wireless interfaces from participating in network bridges. -Create the bridge0 interface with the host network interface as a +Create the https://man.openbsd.org/bridge";>bridge(4) interface with the host network interface as a bridge port. In this example, the host network interface is em0 - you should substitute the interface name that you wish to connect the VM to:
security.html -> patch
Hi @all, in an attachment you can find one more patch for *security.html page. Link: https://www.openbsd.org/security.html please confirm. -Oleg Pahl Index: security.html === RCS file: /cvs/www/security.html,v retrieving revision 1.438 diff -u -r1.438 security.html --- security.html 19 Feb 2019 10:17:31 - 1.438 +++ security.html 19 Feb 2019 10:50:37 - @@ -136,7 +136,7 @@ have fixed many simple and obvious careless programming errors in code and only months later discovered that the problems were in fact exploitable. (Or, more likely someone on -http://online.securityfocus.com/archive/1";>BUGTRAQ +https://www.securityfocus.com/archive/1";>BUGTRAQ would report that other operating systems were vulnerable to a `newly discovered problem', and then it would be discovered that OpenBSD had been fixed in a previous release). In other cases we have been saved @@ -178,7 +178,7 @@ Our proactive auditing process has really paid off. Statements like ``This problem was fixed in OpenBSD about 6 months ago'' have become commonplace in security forums like -http://online.securityfocus.com/archive/1";>BUGTRAQ. +https://www.securityfocus.com/archive/1";>BUGTRAQ. The most intense part of our security auditing happened immediately before the OpenBSD 2.0 release and during the 2.0->2.1 transition, Index: security.html === RCS file: /cvs/www/security.html,v retrieving revision 1.438 diff -u -r1.438 security.html --- security.html 19 Feb 2019 10:17:31 - 1.438 +++ security.html 19 Feb 2019 10:50:37 - @@ -136,7 +136,7 @@ have fixed many simple and obvious careless programming errors in code and only months later discovered that the problems were in fact exploitable. (Or, more likely someone on -http://online.securityfocus.com/archive/1";>BUGTRAQ +https://www.securityfocus.com/archive/1";>BUGTRAQ would report that other operating systems were vulnerable to a `newly discovered problem', and then it would be discovered that OpenBSD had been fixed in a previous release). In other cases we have been saved @@ -178,7 +178,7 @@ Our proactive auditing process has really paid off. Statements like ``This problem was fixed in OpenBSD about 6 months ago'' have become commonplace in security forums like -http://online.securityfocus.com/archive/1";>BUGTRAQ. +https://www.securityfocus.com/archive/1";>BUGTRAQ. The most intense part of our security auditing happened immediately before the OpenBSD 2.0 release and during the 2.0->2.1 transition,
security.html -> broken link
Hi @all, On https://www.openbsd.org/security.html there is a broken link. ---> Full Disclosure Like many readers of theBUGTRAQ mailing list <http://online.securityfocus.com/archive/1>, we believe in full disclosure of security problems. * http://online.securityfocus.com/archive/1 <--- Please check! BR, Oleg Pahl
PKG_SIGN(1) - D argument
Hi @all, Is it ok, that on man page *PKG_SIGN(1)* there is*[-D name=[value]]* argument, but there is no info about value of arg. below ... (I mean what kind of value's is possible to use with -D) I think, that its will be better to put this Info on man page. Not just for me =) Many thx for all. BR, Oleg Pahl
Re: man -> vim
Perfect ! Thanks all ! On 2/15/19 11:35 AM, Otto Moerbeek wrote: On Fri, Feb 15, 2019 at 11:19:57AM +0100, Oleg Pahl wrote: Hi @all, Today I try to work with man pages using *vim*. *# man man | vim -* why i see raw (a lot of special char.) data by default? is it ok? *# ma man | less * I see no special characters. looks very good. Is it possible to convert *raw* data of man page to normal format (for *vim*) with one command? BR, -op Pipe through col -b -Otto
man -> vim
Hi @all, Today I try to work with man pages using *vim*. *# man man | vim -* why i see raw (a lot of special char.) data by default? is it ok? *# ma man | less * I see no special characters. looks very good. Is it possible to convert *raw* data of man page to normal format (for *vim*) with one command? BR, -op
firmware.openbsd.org (SHA256)
Hi all, I use 6.4 Release. I install fm on my laptop from http://firmware.openbsd.org/firmware/6.4/ This URL i found in man page FW_UPDATE(1) You can see that ( index.txt ) has one file more then as on server! --- From index.txt: -rw-r--r-- 1 0 0 1707 Oct 16 22:41:37 2018 SHA256 --- This file I need to check that NSA don't ... Please explain me why this file is absent on -> firmware.openbsd.org BR, Oleg Pahl / Index of 6.4/ drwxr-xr-x 2019-02-12 13:53../ <http://firmware.openbsd.org/firmware/> -r--r--r-- 18572018-10-16 22:41SHA256.sig <http://firmware.openbsd.org/firmware/6.4/SHA256.sig> -r--r--r-- 132269 2018-10-16 22:41acx-firmware-1.4p5.tgz <http://firmware.openbsd.org/firmware/6.4/acx-firmware-1.4p5.tgz> -r--r--r-- 175991 2018-10-16 22:41athn-firmware-1.1p4.tgz <http://firmware.openbsd.org/firmware/6.4/athn-firmware-1.1p4.tgz> -r--r--r-- 9464409 2018-10-16 22:41bwfm-firmware-20171125.tgz <http://firmware.openbsd.org/firmware/6.4/bwfm-firmware-20171125.tgz> -r--r--r-- 39394 2018-10-16 22:41bwi-firmware-1.4p4.tgz <http://firmware.openbsd.org/firmware/6.4/bwi-firmware-1.4p4.tgz> -r--r--r-- 16762018-10-16 22:41index.txt <http://firmware.openbsd.org/firmware/6.4/index.txt> -r--r--r-- 1586910 2018-10-16 22:41intel-firmware-20180807p0v0.tgz <http://firmware.openbsd.org/firmware/6.4/intel-firmware-20180807p0v0.tgz> -r--r--r-- 250278 2018-10-16 22:41ipw-firmware-1.3p2.tgz <http://firmware.openbsd.org/firmware/6.4/ipw-firmware-1.3p2.tgz> -r--r--r-- 272109 2018-10-16 22:41iwi-firmware-3.1p2.tgz <http://firmware.openbsd.org/firmware/6.4/iwi-firmware-3.1p2.tgz> -r--r--r-- 4139154 2018-10-16 22:41iwm-firmware-0.20170105.tgz <http://firmware.openbsd.org/firmware/6.4/iwm-firmware-0.20170105.tgz> -r--r--r-- 3233866 2018-10-16 22:41iwn-firmware-5.11p1.tgz <http://firmware.openbsd.org/firmware/6.4/iwn-firmware-5.11p1.tgz> -r--r--r-- 140369 2018-10-16 22:41malo-firmware-1.4p4.tgz <http://firmware.openbsd.org/firmware/6.4/malo-firmware-1.4p4.tgz> -r--r--r-- 49935 2018-10-16 22:41otus-firmware-1.0p1.tgz <http://firmware.openbsd.org/firmware/6.4/otus-firmware-1.0p1.tgz> -r--r--r-- 162130 2018-10-16 22:41pgt-firmware-1.2p4.tgz <http://firmware.openbsd.org/firmware/6.4/pgt-firmware-1.2p4.tgz> -r--r--r-- 5218724 2018-10-16 22:41radeondrm-firmware-20170119.tgz <http://firmware.openbsd.org/firmware/6.4/radeondrm-firmware-20170119.tgz> -r--r--r-- 65551 2018-10-16 22:41rsu-firmware-1.2p1.tgz <http://firmware.openbsd.org/firmware/6.4/rsu-firmware-1.2p1.tgz> -r--r--r-- 75328 2018-10-16 22:41rtwn-firmware-20180103.tgz <http://firmware.openbsd.org/firmware/6.4/rtwn-firmware-20180103.tgz> -r--r--r-- 73476 2018-10-16 22:41uath-firmware-2.0p1.tgz <http://firmware.openbsd.org/firmware/6.4/uath-firmware-2.0p1.tgz> -r--r--r-- 24371 2018-10-16 22:41upgt-firmware-1.1p4.tgz <http://firmware.openbsd.org/firmware/6.4/upgt-firmware-1.1p4.tgz> -r--r--r-- 63587 2018-10-16 22:41urtwn-firmware-20180103.tgz <http://firmware.openbsd.org/firmware/6.4/urtwn-firmware-20180103.tgz> -r--r--r-- 68204 2018-10-16 22:41uvideo-firmware-1.2p2.tgz <http://firmware.openbsd.org/firmware/6.4/uvideo-firmware-1.2p2.tgz> -r--r--r-- 45960 2018-10-16 22:41vmm-firmware-1.11.0p0.tgz <http://firmware.openbsd.org/firmware/6.4/vmm-firmware-1.11.0p0.tgz> -r--r--r-- 66182 2018-10-16 22:41wpi-firmware-3.2p1.tgz <http://firmware.openbsd.org/firmware/6.4/wpi-firmware-3.2p1.tgz>
CRYPTO CONTAINER
Hi All, Linux has one tool CRYPTSETUP. With this tool I can prepare one container, then open it put some private data and close. I know that our OpenBSD is also Crypto Paranoid OS. Any idea how can I do the same procedure using OBSD default tools? What is recommended work flow for it (to secure file/data) ? P.S. I have full encrypted hard disk. But its not enough for me. Many thx for strong support. BR, deface
