Threads for dlg | Lobsters

12

dlg 17 days ago | link | on: What are you doing this weekend?

Lab 3 on http://deadbeefsociety.org/bootcamp.html.
1. 3
  
  faehnrich 17 days ago | link
  
  That looks neat, bookmarking for later, thanks.
2. 1
  
  admg 16 days ago | link
  
  Bookmarking that one as well, looks well worth going through!

8

Leonidas 10 months ago | link | on: Everything that is wrong with sudo, and how I fixed it

Why? because it’s written in C, and I really don’t want to maintain C code.

Yeah, I can see the point. A weak type system, memory unsafety, surprising behaviour. All good reasons not to write a security relevant tool in C in 2017.

implemented in modern C++

Had a good laugh about this.
1. 1
  
  dlg 10 months ago | link
  
  i found the use of PCRE funny too for the same reason.

4

dlg 12 months ago | link | on: What alternatives to Pandoc do you use on OpenBSD?

i’ve installed pandoc into my homedir on an openbsd box using cabal.
1. 2
  
  jackivan88 12 months ago | link
  
  So you installed haskell-platform using pkg_add and then installed pandoc via cabal without having to build from source? Do you have any specific recommendations, or does this guide match what you did?
  1. 11
    qbit OpenBSD Developer 12 months ago | link
    
    If you are using the standard OpenBSD disk layout (with wxallowed only on /usr/local) you will have to take a few extra steps.
    
    Set the TEMPDIR environment variable to a direct inside of /usr/local.
    
    Make a cable for in /usr/local and symlink it to ~/.cabal
    
    Once that is done, you can use cabal to install pandoc.

3

dlg edited 1 year ago | link | on: Which is better: longer password or more varied characters?

the draft nist guidelines look pretty relevant to this question: https://pages.nist.gov/800-63-3/.

https://nakedsecurity.sophos.com/2016/08/18/nists-new-password-rules-what-you-need-to-know/ is easier to read though.

12

apy 2 years ago | link | on: Samsung acquires Joyent: A CTO’s perspective

Congratulations! Does this mean that Joyent will have the HR infrastructure to start hiring remote workers in Europe?? :)
1. 25
  
  bcantrill 2 years ago | link
  
  That’s exactly what it means – among other things. ;) jobs@joyent.com!
  1. 3
    
    trousers 2 years ago | link
    
    Congrats! Must be exciting times over there.
    1. 6
      
      jclulow 2 years ago | link
      
      Thanks! We’re all pretty stoked over here.
  2. 1
    
    dlg 2 years ago | link
    
    if you need an office in brisbane australia, ive got one ready to go ;)
    
    itd be nice to have alex back too.

1

dlg 2 years ago | link | on: What are you reading this week?

nemesis games by james s a corey, and introduction to algorithms by cormen et al

2

dlg 2 years ago | link | on: What are you working on this week?

im writing a driver supporting megaraid sas fusion chips for illumos, cos the existing mr_sas driver isn’t very good.

1

dlg 2 years ago | link | on: Which shell do you use?

ksh and bash

5

feld 2 years ago | link | on: PostgreSQL - Add BSD authentication method

Does anyone know the history of why only OpenBSD has BSD Auth?

https://en.wikipedia.org/wiki/BSD_Authentication
1. brynet OpenBSD Developer 2 years ago | link
  
  [Comment removed by author]
  1. 2
    
    dlg 2 years ago | link
    
    think of bsdauth as a framework for auth microservices.
2. 9
  
  jcs OpenBSD Developer 2 years ago | link
  
  We didn’t like PAM.
3. 1
  
  mjn 2 years ago | link
  
  Despite the name, BSD Auth isn’t part of the historical BSD codebase that Free/Open/NetBSD forked from, or else it probably would be found across the BSDs. It was a proprietary extension shipped only in BSD/OS, so none of the free-software BSDs had it until OpenBSD dug it up out of BSD/OS’s shallow grave.
  1. 2
    
    tedu 2 years ago | link
    
    I may be mistaken about the timeline, but I think bsdi tried to give bsd auth to FreeBSD before openpam started. I’m not sure why it was rejected, before my time.
    1. 1
      
      feld 2 years ago | link
      
      Yeah, I’m curious why FreeBSD didn’t take it as well
    2. 1
      
      mjn 2 years ago | link
      
      I did a bit of searching in the FreeBSD mailing list archives before posting that and didn’t really turn anything up. As far as I can tell there was never any kind of discussion about it either way, at least on the public mailing lists. So it’s possible that if BSDi did try to donate it to FreeBSD, it got lost in some bitbucket somewhere and never got serious consideration.
      
      The only message at all I can find trying to bring it up is this one from 2001 where someone noticed OpenBSD’s new support for it, and asks if FreeBSD should follow suit (but the query got not replies).
      1. 1
        
        tedu 2 years ago | link
        
        Right. I tried searching again, but didn’t find much. I suppose I could break down and ask people, but a public record would be preferable. Anyway, your comment about digging it out of the grave made me look because bsd/os wasn’t entirely dead at the time. :)
        
        1
        
        tedu 2 years ago | link
        
        For the record, I asked millert and he got the BSD auth code directly from the BSDi people.
        
        1
        
        calvin 2 years ago | link
        
        There’s a difference between mostly dead and all dead. All dead, is well, dead. Mostly dead means they still got something to live for, like selling their organs to the free software that will make them all dead.
        
        1
        
        vadik 2 years ago | link
        
        I also have false memories about such events, which means either that we have been blasted by the same orbital mind laser operated by BSDI, or that what we’re recalling is integration of login_cap(3). It seems like both originated in BSD/OS, as indicated by the HISTORY section of the man pages:
        
        OpenBSD:
        
        The login_getclass function first appeared in OpenBSD 2.8.
        
        NetBSD:
        
        The login_getclass family of functions are largely based on the BSD/OS implementation of same, and appeared in NetBSD 1.5 by kind permission.
        
        FreeBSD:
        
        (tactfully staying silent on the matter, but code committed in early 1997)