Re: Manual to cd (change working directory)
La 13.12.2017 23:36, Niels Kobschaetzki a scris: […] > On Linux the man page for bash opens, […] Not necessarily true, on my Hardened Gentoo this is the first page of what I get for "man cd" (sorry for the wrapping): CD(1P) POSIX Programmer's Manual CD(1P) PROLOG This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. NAME cd — change the working directory SYNOPSIS cd [−L|−P] [directory] cd − signature.asc Description: OpenPGP digital signature
Re: Free OpenBSD Puffy Stickers
On Mon, December 4, 2017 7:58 am, x9p wrote: > forgot subject. > >> Hi, >> >> I ordered about 40 stickers 10x10 to see if quality is ok with local >> maker. They arrive in a week or 2. >> >> Intention isnt to make money out of it for myself, I can post via mail >> to >> the ones willing to try/see the sticker quality - maybe is crappy, who >> knows... >> >> Just send me your name+address. I will be posting from Rio de Janeiro / >> Brazil, if mail fee gets expensive to me, will ask the ones who want the >> sticker to cover it via BTC or Paypal. >> >> If project agrees, I am fine with putting them in an online store and >> forwarding the income to the project, minus expenses of the maker. >> >> cheers. >> >> x9p >> >> > > > maker finished, stickers arriving. still plenty to send. cheers. -- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Any typical pf.conf or sysctl settings to tweak/speedup NAT/networking stack throughput? (+ don't use USB dongles?)
Hi! Do you see any typical pf.conf or sysctl settings to tweak/speedup NAT/networking stack throughput? (On USB2 dongles, sigh. Current speed is quite OK actually, a client with good hardware would get up to 70mbps through the NAT. I was still curious to know if there are any obvious toggles in sysctl/pf.conf for up:ing NAT/networking stack throughput though. RAM is not an issue with me, I have plenty. I thought possibly some settings were set to unnecessarily low defaults, for OpenBSD to work well on machines with <1GB RAM, say.) Tinker
[OT] how secure is 2 factor auth with a smartphone?
Hello guys, I apologize if the subject is too much out of topic for this list. Today I was surprised by hearing from a security (?) tech guy that using 2 factor authentication with AWS was not problem at all when using a smartphone not provided by the company (my own, in the case) that has several VMs on this provider. Considering that the company (my customer in this case) has absolutely no control of whatever I install or how do I use my smartphone, it seems pretty naive to think it is secure enough. It seems to me more an excuse to make professionals like me to pay the bill (the smartphone itself, instead of doing the right thing and buying the MFA device, if security is really the concern here) and probably the legal responsibility too. I've being doing a (basically useless nowadays) effort of avoiding a smartphone due lack of freedom, privacy and terrible cost-benefits (at least here in Brazil, where not only smartphones being expensive, but the associated service that also sucks big time). I did some research in this list archives and couldn't find mention about it. This article shed some light about the subject: https://www.csoonline.com/article/3044605/security/does-a-smartphone-make-two-factor-authentication.html What do you guys think about? Do you agree with the article author opinion? Feeling like a Neanderthal here, doesn't matter if a lot of people on the streets nowadays look like those spaceship characters of the WALL-E movie... Thanks, Alceu
Re: Manual to cd (change working directory)
On Wed, December 13, 2017 9:24 pm, edgar wrote: > > > I'm going to start an openbsd blog with nothing but ingo misc@ posts. > +1. I also felt some enlightenment reading his answer. cheers. -- x9p | PGP : 0x03B50AF5EA4C8D80 / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Manual to cd (change working directory)
I'm going to start an openbsd blog with nothing but ingo misc@ posts. > > On Dec 13, 2017 at 3:52 PM,wrote: > > > Hi Freddy, Freddy Fisker wrote on Wed, Dec 13, 2017 at 10:22:32PM +0100: > > I can't get the manual to the cd (change working directory) command. That is > not a stand-alone command, but a shell built-in. Actually, it is not even > possible to implement it as a stand-alone command because the effect of the > intended change would end when the command exits. > When I am trying, I get > the manual to cd (ATAPI and SCSI CD-ROM driver) > instead. > > It's the > same with: man cd > > and in: https://man.openbsd.org/cd In general, when > man(1) gives you the wrong section, specify the section: $ man 1 cd > https://man.openbsd.org/cd.1 Of course, in the specific case at hand, that > won't help because no such manual exists. Your next try if a manual you are > looking for does not exist should be something like $ man -k any~^cd\$ See > apropos(1) for details what "any", ~, ^, and $ mean. That gives you about a > dozen results, and the shell manuals you are looking for are among them. If > you want le ss noise, you can guess that cd is probably some kind of command, so a more specific try would be schwarze@isnote $ man -k Ic,Cm~^cd\$ csh(1) - a shell (command interpreter) with C-like syntax ftp(1) - Internet file transfer program help(1) - help for new users and administrators ksh, rksh(1) - public domain Korn shell mail, Mail, mailx(1) - send and receive mail sftp(1) - secure file transfer program sh(1) - command language interpreter vi, ex, view(1) - text editors azalia(4) - generic High Definition Audio device fsdb(8) - FFS debugging/editing tool restore, rrestore(8) - restore files or file systems from backups... You see, almost no false positives are left - ftp(1), sftp(1), restore(1), and even vi(1) indeed have internal cd commands, too. If you are completely desperate, you can even say $ man -ak Ic,Cm~^cd\$ to get all these manuals in your pager together, then type :tcd inside less(1) to get to the first place where "cd" is defined, then press just t repeatedly to move on to the other places in turn. Admittedly, that way, it's a bit hard to see which manual you are looking at at any specific time, but when you find an instance that pleases you, you can type ?^NAME inside less to see the start of the respective manual to see its name. After that, you can use the "t", "T", and "n" keys alternatingly to move around among instance and see in which manual they are in. So we just learned that at least nine different cd commands are documented in various places, rather than cd not being documented at all. Which is the one you want to use? Learn to use your documentation tools! =:c) Yours, Ingo >
Re: Manual to cd (change working directory)
On Wed, Dec 13, 2017 at 10:22:32PM +0100, Freddy Fisker wrote: > Hi > > I can't get the manual to the cd (change working directory) command. When I > am trying, I get the manual to cd (ATAPI and SCSI CD-ROM driver) instead. > > It's the same with: man cd > > and in: https://man.openbsd.org/cd The others already provided plenty of help with regard to manual pages, however the shell itself may help you out, too: $ type cd cd is a shell builtin To illustrate this further: $ types an alias for 'whence -v' $ type whence whence is a shell builtin ksh(1) has all the details about (special) builtins; of course there is a tag for `whence' so :twhence as described already by Ingo will bring you right to it.
Re: Manual to cd (change working directory)
Hi Freddy, Freddy Fisker wrote on Wed, Dec 13, 2017 at 10:22:32PM +0100: > I can't get the manual to the cd (change working directory) command. That is not a stand-alone command, but a shell built-in. Actually, it is not even possible to implement it as a stand-alone command because the effect of the intended change would end when the command exits. > When I am trying, I get the manual to cd (ATAPI and SCSI CD-ROM driver) > instead. > > It's the same with: man cd > > and in: https://man.openbsd.org/cd In general, when man(1) gives you the wrong section, specify the section: $ man 1 cd https://man.openbsd.org/cd.1 Of course, in the specific case at hand, that won't help because no such manual exists. Your next try if a manual you are looking for does not exist should be something like $ man -k any~^cd\$ See apropos(1) for details what "any", ~, ^, and $ mean. That gives you about a dozen results, and the shell manuals you are looking for are among them. If you want less noise, you can guess that cd is probably some kind of command, so a more specific try would be schwarze@isnote $ man -k Ic,Cm~^cd\$ csh(1) - a shell (command interpreter) with C-like syntax ftp(1) - Internet file transfer program help(1) - help for new users and administrators ksh, rksh(1) - public domain Korn shell mail, Mail, mailx(1) - send and receive mail sftp(1) - secure file transfer program sh(1) - command language interpreter vi, ex, view(1) - text editors azalia(4) - generic High Definition Audio device fsdb(8) - FFS debugging/editing tool restore, rrestore(8) - restore files or file systems from backups... You see, almost no false positives are left - ftp(1), sftp(1), restore(1), and even vi(1) indeed have internal cd commands, too. If you are completely desperate, you can even say $ man -ak Ic,Cm~^cd\$ to get all these manuals in your pager together, then type :tcd inside less(1) to get to the first place where "cd" is defined, then press just t repeatedly to move on to the other places in turn. Admittedly, that way, it's a bit hard to see which manual you are looking at at any specific time, but when you find an instance that pleases you, you can type ?^NAME inside less to see the start of the respective manual to see its name. After that, you can use the "t", "T", and "n" keys alternatingly to move around among instance and see in which manual they are in. So we just learned that at least nine different cd commands are documented in various places, rather than cd not being documented at all. Which is the one you want to use? Learn to use your documentation tools! =:c) Yours, Ingo
Re: Manual to cd (change working directory)
On 17/12/13 22:22, Freddy Fisker wrote: I can't get the manual to the cd (change working directory) command. When I am trying, I get the manual to cd (ATAPI and SCSI CD-ROM driver) instead. It's the same with: man cd and in: https://man.openbsd.org/cd cd is a built-in in a shell. So, you need to do "man ksh" or "man sh" or whatever shell you use. On Linux the man page for bash opens, on FreeBSD it is the man page for built-ins, when you do "man cd". Cheers, Niels
Re: Manual to cd (change working directory)
On Wed, Dec 13, 2017 at 10:22:32PM +0100, Freddy Fisker wrote: > Hi > > I can't get the manual to the cd (change working directory) command. When I > am trying, I get the manual to cd (ATAPI and SCSI CD-ROM driver) instead. > > It's the same with: man cd > > and in: https://man.openbsd.org/cd There's no manual for cd, as it's a shell built-in. You need to consult the manual of your shell for more info. The sh(1), ksh(1) and csh(1) pages all contain a few paragraphs on cd. > Best regards > Freddy >
Manual to cd (change working directory)
Hi I can't get the manual to the cd (change working directory) command. When I am trying, I get the manual to cd (ATAPI and SCSI CD-ROM driver) instead. It's the same with: man cd and in: https://man.openbsd.org/cd Best regards Freddy
Re: AuthorizedKeyCommand ldap
> > > The script they call acts similar to this > > > > > > user="$1" > > case $user in > user1) > do stuff > ;; > user2) > do stuff > ;; > > user3) > do stuff > ;; > *) > invalid user stuff > ;; A solution that scales would use a regex that checks input for chars not allowed in a username, and confirms the length of input doesn't exceed the max length for a username.
how to properly rebuild or delete crypto softraid?
I have successfully built an encrypted bootable usb according to the instructions https://www.openbsd.org/faq/faq14.html#softraidFDE After booting successfully several times, the device went to ddb after I installed chrome without previously adding xfonts during the install. Subsuequent attempts to boot were unsuccessfull. I have erased partitions by disklabel and fdisk and tried to repeat the installation process. However, the encrypted raid device appeared and I was able to unlock it by the same passphrase, so I ceased the installation. Is it possible to delete the crypto raid properly at this stage? Should I tri to rebuild it? Any advice is appreciated. Thanks in advance.
Re: syspatch not updating kernel
Steven Surdock wrote: > I just ran syspatch on a 6.2/i386 host and the kernel did not change as > it = > has on my other patched machines. It appears that > pub/OpenBSD/syspatch/6.2= > was updated on 12/10. > > root@rad03 [/root]# syspatch -l > 002_fktrace > 003_mpls > root@rad03 [/root]# uname -a > OpenBSD cts-rad03.ctstelecom.com 6.2 GENERIC.MP#166 i386 > > > -Steve S. Steve, Anything in the log files? Is /var/db/kernel.SHA256 empty? Do you run sp kernel on the machine capable of multi processing? Check out the misc archive for various "syspatch bug reports". Most if not all of them were trivial omissions on the part of the user (I am a culprit of one such fake report myself). Predrag
syspatch not updating kernel
I just ran syspatch on a 6.2/i386 host and the kernel did not change as it has on my other patched machines. It appears that pub/OpenBSD/syspatch/6.2 was updated on 12/10. root@rad03 [/root]# syspatch -l 002_fktrace 003_mpls root@rad03 [/root]# uname -a OpenBSD cts-rad03.ctstelecom.com 6.2 GENERIC.MP#166 i386 -Steve S.
