mr browns exploit and set up trouble

gamster · Post by **gamster** » Sun Mar 12, 2006 6:39 am

It says in the read me that you can use another exploit with the cnf,

Quote:

There is another exploit that can be triggered exactly like this one, except
it lives on the PS1 disc in SYSTEM.CNF.

I don't have a method to manufacturevalid PS1 discs, so this exploit doesn't interest me much.

Developing code for this exploit is an excercise left to the reader.

Quote.

My first question is this, since you can swap out a psx disk on the v12, couldn't you use this to boot homebrew on the v12?

I'm also having trouble getting PS2Dev_Setup working on cygwin, I'm trying to get the hello world application to make.

I recive the following error when trying to make:

makefile:20: /samples/Makefile.pref: No such file or directory
makefile:21: /samples/Makefile.eeglobal: No such file or directory
C:\cygwin\usr\local\ps2dev\bin\make.exe: *** No rule to make target '/samples/Makefile.eeglobal'. Stop

I know the files are there I've checked, and I'm prettey sure I got the paths set up right, but I'm a noob at this sooo.

ubergeek42 · Post by **ubergeek42** » Sun Mar 12, 2006 7:40 am

that is the result of missing environment variables...
in the readme it says to set PS2DEV, PS2SDK, and to update your PATH environment variables.

you can add these to the .bashrc file in your users directory i believe..
the directory should be something like c:\cygwin\home\username\
if the file does not exist create it.

gamster · Post by **gamster** » Sun Mar 12, 2006 8:27 am

I have a bashrc but it is located inC:cgywin/etc/ I have it set up like this:

# base-files version 3.7-1

# WARNING
#
# IF THIS bash IS MODIFIED IT WILL NOT BE UPDATED BY THE CYGWIN
# SETUP PROGRAM. IT BECOMES YOUR RESPONSIBILITY.
#
# The latest version as installed by the Cygwin Setup program can
# always be found at /etc/defaults/etc/bash.bashrc

# System-wide .bashrc file

## PS2DEV SETTINGS
export PS2DEV="/usr/local/ps2dev"
export PS2SDK="$PS2DEV/ps2sdk"
export PATH="$PATH:$PS2DEV/bin:$PS2DEV/ee/bin:$PS2DEV/iop/bin:$PS2DEV/dvp/bin:$PS2SDK/bin"
export PS2LIB="$PS2SDK/ps2lib"
export GSKIT="$PS2SDK/gsKit"
export LIBITO="$PS2DEV/libito"

Is everything set up the way its supposed to be?

ubergeek42 · Post by **ubergeek42** » Sun Mar 12, 2006 8:40 am

that looks right, but there must be something wrong, what happens when you type

echo $PS2DEV

it should output /usr/local/ps2dev otherwise something is not right.
maybe try copying that into your userspecific .bashrc file?

or add an echo line to that(the global one) file, like
echo "this is the global bashrc file being used"
then if you see that when you open a console, you know it worked..

bbchazz · Post by **bbchazz** » Sun Mar 12, 2006 12:07 pm

What if you be a little more specific with the PS2DEV export line. You current have:

export PS2DEV="/usr/local/ps2dev"

Why not try

export PS2DEV="c:/cygwin/usr/local/ps2dev"

ubergeek42 · Post by **ubergeek42** » Sun Mar 12, 2006 12:56 pm

that might work, but i don't think its his problem, i think the variables are not even being set to anything. because it says:

makefile:20: /samples/Makefile.pref: No such file or directory
makefile:21: /samples/Makefile.eeglobal: No such file or directory
C:\cygwin\usr\local\ps2dev\bin\make.exe: *** No rule to make target '/samples/Makefile.eeglobal'. Stop

if you look at a makefile, before the words /samples/Makefile.pref, it has $(PS2DEV) and since there is nothing before the /samples word in the output of the make command, i am lead to believe that this variable holds nothing, not the wrong information

gamster · Post by **gamster** » Sun Mar 12, 2006 3:06 pm

I typed echo $PS2DEV and nothing happened. How would I copy that into my bashrc?

I also tried to echo my makefile.pref and it repeated my paths.

I tried changing the bashrc from export PS2DEV="/usr/local/ps2dev"
to export PS2DEV="c:/cygwin/usr/local/ps2dev".

Dr. Vegetable · Post by **Dr. Vegetable** » Sun Mar 12, 2006 11:29 pm

I think the poll at the top of this thread is written incorrectly. It should read:

Wouldn't booting homebrew on the slimline be cool?
(*) Duh!

ubergeek42 · Post by **ubergeek42** » Mon Mar 13, 2006 2:03 am

well you would open your bashrc file with notepad or the like, and copy and paste the export statements into it.

gamster · Post by **gamster** » Mon Mar 13, 2006 2:31 am

Sorry I meant how would I accomplish this:

or add an echo line to that(the global one) file, like
echo "this is the global bashrc file being used"
then if you see that when you open a console, you know it worked

dmcbudman · Post by **dmcbudman** » Mon Mar 13, 2006 4:38 am

about the topic of this thread
i thinks its highly probable that sony never fixed the system.cnf overflow vulnerability
and given the fact that slimline playstations can easily load homebrew ps1 discs,
i believe that there is a good chance for a slimline exploit.
i was tring to stress this point on irc the other day before i got banned for speaking of "warez" (and didnt want to continue the discution any farther after i rejoined)

i was also told

Since legally its shady no one's done/released it and i doubt ever will.

what kind of legalities are involved here?
its my thought that this would be a totaly legal and valid exploit (unless it would involve copyrighted files)

anyways
if anyone could shed shed some light on this, please do

gamster · Post by **gamster** » Mon Mar 13, 2006 2:17 pm

I'd like to know why its legally shady, as its one of my current projects when I get this done I was wondering if I'll be able to upload it and distribute it.

If anyone can help us understand the legalitys issues surrounding this it would be greatly appriciated.

cheriff · Post by **cheriff** » Mon Mar 13, 2006 2:46 pm

I think it might have been me who said that on IRC... I probably should elaborate.

What I meant by it, is that the system.cnf exploit is redundant: if you can get the ps2 to read a hacked system.cnf off a CD, then you have no use for the exploit since you can already read burnt cd's, so I do not see the point of this exploit. Of course it's legal, just also perfectly useless.

Also, the direction in which the discussion was going, seemed to be towards finding a way to boot "backup PS1 disks" which a) is useless for ps2 homebrew, and b) is only a short step away from booting downloaded iso's or whatever - hence the shady legality. Arguments on whether or not we have the right to do so belongs on some other forum, but history has shown that as soon as any dev technique has the potential to boot a commercial title, some jerk will do so and next thing you know hundreds of kids are downloading warez "thanks to the guys at ps2dev.org".

Which is why people have tended to distance themselves from tools and such that aren't strictly a requirement for booting homebrew. If you really really, REALLY want to run your own code on a slimline and cant buy the ps2 linux DVD, then by all means, buy a modchip. Whilst they can also be used for evil, the cost and hassle alone will deter most of the casual scriptkiddies that will flock to a softmod.

I'm not trying to deter anyone from participating around here, just let it be known that mentioning the 'backups' in general will attract hostility. Other than that, good luck & have fun! :)

- cheriff

gamster · Post by **gamster** » Sun Mar 19, 2006 5:45 am

Come on someone has to know why it can't detect my files? I did a complete reinstall and still no luck.

I just want to compile hello world. "Pulls hair out in frustration"

tumnes · Post by **tumnes** » Sun Mar 19, 2006 6:23 am

I'm pretty sure you want to changed those settings in the .bashrc file in your home directory. I remember something about cygwin not letting you change the global bashrc file.

Makefile.pref and Makefile.eeglobal are located in $PS2SDK/samples, make sure this is what it says in the Makefile, for the project you are trying to build. I think I have had to change it in the past to make some things compile.

Post by **Neovanglist** » Sun Mar 26, 2006 1:04 pm

Booting homebrew on slimline is already possible with the RTE(ps2linux)/reload1 exploit.

gamster · Post by **gamster** » Mon Apr 03, 2006 3:03 pm

Whats the RTE(ps2linux)/reload1 exploit?

cheriff · Post by **cheriff** » Mon Apr 03, 2006 3:07 pm

With the sony ps2linux kit, the RTE dvd boots the linux kernel off the memory card. You can change the configuration file to have it boot something else instead. This usually is a program called reload which 'reloads' the ps2 kernel from ROM (since the RTE has cleared it out previously) and then can boot ps2client.
I don't use it personally, but thats how I understand it to work.

gamster · Post by **gamster** » Mon Apr 03, 2006 11:56 pm

Oh, you need the linux disks.

sneeze · Post by **sneeze** » Thu Apr 06, 2006 7:42 pm

A cheaper alternative to the RTE disc and modchips might be the the newer Action Replay & Swap Magic discs which also lets you boot homebrew sw from memcard and/or usb (at least that's what they claim, I have no personal experience with any of them).