Re: Best way to serve files to Windows?

[Stephen Trotter]

Hey guys.  Just wanted to let you know about the security aspect.

Anything on SMB is passed completely in the clear.

You can actually use Wireshark to carve files directly out of PCAP that
have SMB traffic.

On Wed, Jul 25, 2018 at 1:56 PM Adam Thompson  wrote:

> On 2018-07-18 09:35, Tom Smyth wrote:
> > Hi John,
> > You would need microsoft services for unix (SFU) for NFS connectivity
>
> FYI - so no-one goes haring off in the wrong direction.
>
> SFU is the server-side component, equivalent to running nfsd(8).
>
> On the client side, only certain editions of Windows can speak NFS:
> - Windows 10 *Enterprise* can mount remote NFS shares.
> - Windows 7 *Ultimate* can mount remote NFS shares.
> (No idea about Win8, sorry.)
>
> Win10Ent, at least, has flexible authentication options, but IIRC
> defaults to uid=0/gid=0 (gee, thanks).  It prefers to use Kerberos
> security, which won't work with OpenBSD's NFS server.  It's possible to
> make this work reasonably well, but it takes a fair bit of time.
>
> So, as everyone else said, you're better off running Samba on your
> OpenBSD system.  Have fun.
> -Adam
>
>

xenocara build on fresh install

[Stephen Trotter]

hi, I am just curious if the defaults (namely the disk sizes) are supposed
to be sufficient for building xenocara after a fresh install.

i attempted to do so following release(8) and it ended unsuccessfully due
to the drive/filesystem being full.

(it does seem to have almost finished, by the way)

All I have done else in the system is pulling source and making according
to the faq5 page.  This is after skipping the "release" part and moving on
to building xenocara.

Let me know what else i need to include for assist.

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Thanks again for all the help! I just finished a fresh install, logged in
as root and updated the wsrc group on my user, then after login as the user
was able to start up CVS with no issue at all.  Just wanted to verify.

On Fri, Sep 9, 2016 at 10:33 AM, Theo Buehler <t...@math.ethz.ch> wrote:

> On Fri, Sep 09, 2016 at 10:19:21AM -0400, Stephen Trotter wrote:
> > Aha, this is probably what was going on.  I used su to add my user to the
> > group, then had just exited to my user shell to continue with the faq.
> > I'll probably do a fresh install and ensure it works out, and to make
> sure
> > I don't have any issues with CVS.  Thanks for the help!
>
> I added a couple of clarifications to faq5.html and anoncvs.html to
> avoid this confusion in the future. Thanks for the report.

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Aha, this is probably what was going on.  I used su to add my user to the
group, then had just exited to my user shell to continue with the faq.
I'll probably do a fresh install and ensure it works out, and to make sure
I don't have any issues with CVS.  Thanks for the help!

Stephen J. Trotter

On Fri, Sep 9, 2016 at 9:38 AM, Christian Weisgerber 
wrote:

> On 2016-09-09, Theo Buehler  wrote:
>
> > I tried myself on a fresh install, added my user to wsrc, and I can
> > confirm that I got permission errors (write permissions denied to
> > /usr/src) which went away after logging out and logging in again.
>
> Yes, you have to login again for the new group membership to be
> active.
>
> --
> Christian "naddy" Weisgerber  na...@mips.inka.de

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Also I should mention that I was able to get the commands to work by going
into /usr/src and running from there, but did find afterward that a new
copy of src was put into the folder ( i.e. /usr/src/src/ ) so I did end up
moving everything up a directory. I am not sure, will this affect cvs in
the future, or should I be ok as long as I run it with the full command to
pull the src, from /usr (oppossed to running the update command first)?

On Sep 9, 2016 8:04 AM, "Stephen Trotter" <stephen.j.trot...@gmail.com>
wrote:

> Raf,
>
> Yes I was attempting to follow the instructions and was logged in as my
> user, not as root. And I was pulling the src from cvs (for the first time)
> and using the -r option for the stable version.
>
> Theo,
>
> The user is a member of wsrc. That was part of the reason I was so
> confused at the time. (I can't verify with id at the moment, but I did
> check /etc/group to ensure the user was listed under wsrc.)
>
> I suspect that /usr is not owned by wsrc possibly, and that cvs was trying
> to write to /usr but I cannot confirm right now. When I am able to, I will
> run cvs again without the -q option and see if there is any extra detail I
> can include.
>
> Thanks, will reply again when I can run those.
>
> (As a side note, should doas be enabled by default? I don't recall any
> instruction in the faq on setting it up, but when I try to use it, it
> fails.)
>
> On Sep 9, 2016 1:20 AM, "Theo Buehler" <t...@math.ethz.ch> wrote:
>
>> On Fri, Sep 09, 2016 at 12:54:05AM -0400, Stephen Trotter wrote:
>> > hi,
>> > i was attempting a fresh install of 6.0 and got to the part where you
>> pull
>> > the source tree and update the system to stable.
>> > i was stuck because the faq states you can (should) use a regular user
>> with
>> > cvs, and i kept getting a permission error from cvs when attempting to
>> run
>> > from /usr
>> > so, just wondering if anyone else was getting this, or if there is
>> > something that i missed.
>> >
>>
>> Is your user member of the group wsrc?  Use id(1), for example.
>>
>> By default, /usr/src is owned by root:wsrc with permissions 0775.  This
>> means that you need to be root or a member of group wsrc in order to
>> write to it.  FAQ 5 'avoiding root' tells you how to add your user to
>> wsrc before running cvs: user mod -G wsrc youruser

Re: fresh install of 6.0 - cvs

[Stephen Trotter]

Raf,

Yes I was attempting to follow the instructions and was logged in as my
user, not as root. And I was pulling the src from cvs (for the first time)
and using the -r option for the stable version.

Theo,

The user is a member of wsrc. That was part of the reason I was so confused
at the time. (I can't verify with id at the moment, but I did check
/etc/group to ensure the user was listed under wsrc.)

I suspect that /usr is not owned by wsrc possibly, and that cvs was trying
to write to /usr but I cannot confirm right now. When I am able to, I will
run cvs again without the -q option and see if there is any extra detail I
can include.

Thanks, will reply again when I can run those.

(As a side note, should doas be enabled by default? I don't recall any
instruction in the faq on setting it up, but when I try to use it, it
fails.)

On Sep 9, 2016 1:20 AM, "Theo Buehler" <t...@math.ethz.ch> wrote:

> On Fri, Sep 09, 2016 at 12:54:05AM -0400, Stephen Trotter wrote:
> > hi,
> > i was attempting a fresh install of 6.0 and got to the part where you
> pull
> > the source tree and update the system to stable.
> > i was stuck because the faq states you can (should) use a regular user
> with
> > cvs, and i kept getting a permission error from cvs when attempting to
> run
> > from /usr
> > so, just wondering if anyone else was getting this, or if there is
> > something that i missed.
> >
>
> Is your user member of the group wsrc?  Use id(1), for example.
>
> By default, /usr/src is owned by root:wsrc with permissions 0775.  This
> means that you need to be root or a member of group wsrc in order to
> write to it.  FAQ 5 'avoiding root' tells you how to add your user to
> wsrc before running cvs: user mod -G wsrc youruser

fresh install of 6.0 - cvs

[Stephen Trotter]

hi,
i was attempting a fresh install of 6.0 and got to the part where you pull
the source tree and update the system to stable.
i was stuck because the faq states you can (should) use a regular user with
cvs, and i kept getting a permission error from cvs when attempting to run
from /usr
so, just wondering if anyone else was getting this, or if there is
something that i missed.