Need help bypassing login screen without compromising machine security
I'm in a weird situation, i have a dedicated mini pc for my Jellyfin server
Here are the requirements for solutions
I cannot use an interface like a keyboard or mouse
-I will not use linux for this particular machine
-The device does have USB ports and a screen
So to just have the jellyfin server start automatically, i would like to be able to hit the power button and have it boot into windows, thus automatically starting the jellyfin server and allowing me to do server restarts to fix issues.
Problem is the login screen, i can go as far as removing my password but it still requires user input to login. I need to bypass this but on the other hand i would not like to leave this giant vulnerability in my system. Is there any sort of way to get the best of both worlds? to have the PC be able to go from power button to jellyfin server started and still have some measure of security?
Thanks if anyone has any insight to my problem it would be wildly appreciated
Can you set the Jellyfin server service to start with Windows? Shouldn't need a login then. If not, you can use a PowerShell script that starts the Jellyfin .exe and use a scheduled task to run it when event id 6005 is triggered. That's the event id created when the event log starts.
This might work, do you know how secure this is? Could i just put it in to automatically input the password on startup? i imagine that wouldn't just "unlock" the machine for anyone trying to SSH in
Automatically entering the password at the login prompt would be FAR more insecure than task scheduler starting the task on startup. What you should do is go into task scheduler and tell it to start your jellyfin service. Then jellyfin is running, but your user isn't even signed in.
I have used this for something else a few years ago: It let me select what user to run it as and prompted me for a password while configuring it and then later it didn't need a login any more.
Very true. I have a couple items at work that don't work when I pick "at startup" so I usually just go with the event log startup as the trigger nowadays.