Tagged: windows Toggle Comment Threads | Keyboard Shortcuts

  • duncanbowring 22:48 on January 30, 2019 Permalink | Reply
    Tags: cygwin, , rsync, windows   

    Cygwin Rsync Windows Permissions 

    ARGHGHGHGHGHHGHGHGHHGHGHGHGH!!!

    OK, stop this happening:

    Open /etc/fstab and add noacl to the entry:

    none /cygdrive cygdrive binary,noacl,posix=0,user 0 0

    Save it. Close all cygwin terminals and start new terminal.

    Fix the bad stuff that already exists at the destination:

    Change Owner to local Administrator. Save and Apply to Children.
    Edit permissions, fix them up.. then advanced, Advanced.. apply to children (inherit from the new top level one you added).
    After this.. disable read only, apply to children.
    You will be able to delete this mess now.

    permission-screenshot-min

    Advertisements
     
    • psychocod3r 13:44 on February 27, 2019 Permalink | Reply

      I don’t think administrative programs like that are meant to run in Cygwin. The security models used by Linux and Windows are so fundamentally different that it can be near impossible to translate between the two. You’re probably better off just running stuff like this natively in Linux. I tried running pro-ftpd in Cygwin once and it was a nightmare, mostly because there was no documentation available to indicate what specific accounts I needed to create for running the server within Cygwin. Programs that run in Cygwin are not actually Linux programs; they’re Windows programs with a few extra layers of abstraction on top. You have to remember that even though a Cygwin program may feel like it’s running on a Unix system (since that’s what an emulator does after all), it’s really running entirely in the context of Windows and its security model.

      • duncanbowring 13:54 on February 27, 2019 Permalink | Reply

        Hi there. There were a couple of scenarios where I had to do this on Windows. I agree with you, fundamentally.

  • duncanbowring 17:56 on March 27, 2013 Permalink | Reply
    Tags: ip4 to ip6, ipv4 to ipv6, port forward, port redirection, portproxy, proxy ports windows, server 2008 r2, windows, windows port redirection, xinetd   

    Port forward/proxy/redirect – Windows – Just like Xinetd. 

    So, if you have an issue where you need to forward a port to a different location with Windows, you’re in luck. Whilst you don’t have xinetd, you don’t have to use a third party tool or service.

    SYSTEM A – 10.0.0.10

    SYSTEM B – 192.168.0.10

    SYSTEM C – 172.16.0.10

    If you cannot directly route SYSTEM A to SYSTEM C but need to hit a service running on port 25/tcp on SYSTEM C from SYSTEM A, you can use portproxy. Let’s say both sides can hit SYSTEM B. You can use portproxy to set up SYSTEM B to forward your request to SYSTEM C, yet access the same service from SYSTEM A by hitting SYSTEM B.

    Simply at the command prompt on SYSTEM B, type:

    netsh

    interface portproxy

    add v4tov4 listenport=25 connectaddress=172.16.0.10 connectport=25 protocol=tcp

    This means when you now hit 192.168.0.10 on port 25, you’ll receive the data from SYSTEM C’s socket. Simple port proxying or forwarding.

    You can also do this from IPv4 to v6, or v6 to v6.
    Best of all, you can use DNS names.. !!

    Simply add this in as a startup script via a group policy object, and you’ve got your own cross-network router for specific ports.

    Port Proxy documentation at Microsoft:

    http://technet.microsoft.com/en-us/library/cc776297%28WS.10%29.aspx

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel
%d bloggers like this: